Apparatuses, computer-implemented methods, and computer program products for managing a shared dynamic collaborative presentation progression interface in association with an audio-video conferencing interface service

ABSTRACT

Various embodiments of the present disclosure provide for generating, updating, and/or otherwise managing a shared dynamic collaborative presentation progression interface in association with an audio-video conferencing interface service. An example embodiment is configured to monitor an active audio-video conference presentation that is configured for display to participating client devices by the audio-video conference interface service, generate a shared dynamic collaborative presentation progression interface, transmit the shared dynamic collaborative presentation progression interface to the plurality of participating client devices, receive an initiate topic object sequence set event from at least one participating client device of the participating client devices, identify a first topic object of the topic object sequence set as an active topic object, and update the shared dynamic collaborative presentation progression interface render an active visual emphasis element of the first topic object.

BACKGROUND

Applicant has identified a number of deficiencies and problemsassociated with efficiently identifying and effectively disseminatinginformation regarding one or more agenda elements in an audio-videoconference presentation, among a plurality of users in existing systemsthat provide multi-party virtual meeting environments (e.g., audio/videoconferencing). Through applied effort, ingenuity, and innovation, manyof these identified deficiencies and problems have been solved bydeveloping solutions that are structured in accordance with theembodiments of the present disclosure, many examples of which aredescribed in detail herein.

BRIEF SUMMARY

In general, embodiments of the present disclosure provided hereininclude improved apparatuses, methods, systems, and computer programproducts configured for generating and updating a shared dynamiccollaborative presentation progression interface in association with anactive audio-video conference presentation provided by an audio-videoconferencing interface service. In accordance with one exemplaryembodiment of the present disclosure, an apparatus is configured tomanage a shared dynamic collaborative presentation progression interfacein association with an audio-video conferencing interface service, theapparatus comprising at least one processor and at least one memory, theat least one memory having computer-coded instructions therein, whereinthe computer-coded instructions are configured to, in execution with atleast one processor, cause the apparatus to: monitor an activeaudio-video conference presentation that is configured for rendering torespective displays of a plurality of participating client devices bythe audio-video conferencing interface service; generate a shareddynamic collaborative presentation progression interface, wherein theshared dynamic collaborative presentation progression interface isassociated with a topic object sequence set and wherein the shareddynamic collaborative presentation progression interface is configuredfor rendering to the respective displays of the plurality ofparticipating client devices in association with the active audio-videoconference presentation; transmit the shared dynamic collaborativepresentation progression interface to the plurality of participatingclient devices; receive an initiate topic object sequence set event fromat least one participating client device of the plurality ofparticipating client devices; in response to receiving the initiatetopic object sequence set event, identify a first topic object of thetopic object sequence set as an active topic object; and update theshared dynamic collaborative presentation progression interface to causerendering of at least an active visual emphasis element in associationwith a visual representation of the first topic object.

In some embodiments, the updated shared dynamic collaborativepresentation progression interface further comprises a visualrepresentation of an elapsed time object displayed in association withthe first topic object. In still further embodiments, the elapsed timeobject corresponds to a timer activated by the apparatus in associationwith identifying the first topic object as the active topic object. Insome embodiments, the shared dynamic collaborative presentationprogression interface further comprises a topic object progressioninterface component.

In some embodiments, the computer-coded instructions are furtherconfigured to, in execution with the at least one processor, cause theapparatus to: receive a topic object progression event from at least oneparticipating client device of the plurality of participating clientdevices; de-identify the first topic object as the active topic object;identify a second topic object in the topic object sequence set as theactive topic object; generate a transition topic object sequenceinstructions set based on the topic object progression event; and outputthe transition topic object sequence instructions set to the pluralityof participating client devices for updating the shared dynamiccollaborative presentation progression interface, wherein updating theshared dynamic collaborative presentation progression interfacecomprises causing: stopping of the rendering of the active visualemphasis element in association with the visual representation of thefirst topic object; and rendering of the active visual emphasis elementin association with the visual representation of the second topicobject.

In some embodiments, the de-identifying of the first topic object as theactive topic object comprises: dissociating an active topic objectidentifier from the first topic object; associating the first topicobject with a completed topic object identifier; and storing the elapsedtime object coinciding with the receipt of the topic object progressionevent in association with the completed first topic object.

In some embodiments, the computer-coded instructions are furtherconfigured to, in execution with the at least one processor, cause theapparatus to: in association with causing stopping of the rendering ofthe active visual emphasis element with respect to the visualrepresentation of the first topic object, cause display of a completionindicator in association with the visual representation of the firsttopic object.

In some embodiments, the computer-coded instructions are furtherconfigured to, in execution with the at least one processor, cause theapparatus to: in association with causing stopping of the rendering ofthe active visual emphasis element with respect to the visualrepresentation of the first topic object, cause display of an annotationsummary in association with the visual representation of the first topicobject. In still further embodiments, the annotation summary comprises asummary listing of content captured in association with the first topicobject during the period of time the first topic object was identifiedas the active topic object.

In some embodiments, the identifying of the second topic object in thetopic object sequence set as the active topic object comprisesassociating the second topic object with an active topic objectidentifier.

In some embodiments, the first participating user identifier isassociated with the first topic object and a second participating useridentifier is associated with the second topic object and wherein thecomputer-coded instructions are further configured to, in execution withthe at least one processor, cause the apparatus to: display a visualrepresentation of the first participating user identifier in associationwith the visual representation of the first topic object; and display avisual representation of the second participating user identifier inassociation with the visual representation of the second topic object.In still further embodiments, the computer-coded instructions arefurther configured to, in execution with the at least one processor,cause the apparatus to: in response to identifying the first topicobject of the topic object sequence set as the active topic object,transmit a display upcoming presenter notification event to theparticipating client device associated with the second participatinguser identifier.

In some embodiments, a plurality of participating user identifiers areassociated with the first topic object and wherein the computer-codedinstructions are further configured to, in execution with the at leastone processor, cause the apparatus to: in response to receiving anidentify random presentation order event, identify a first participatinguser identifier of the plurality of participating user identifiersassociated with the first topic object; cause display of a visualrepresentation of the first participating user identifier in associationwith the visual representation of the first topic object; determine apresenting order of the remaining participating user identifiersassociated with the first topic object; and cause display of visualrepresentations of each of the remaining participating user identifiersin the determined order in association with an upcoming presenterinterface element in the visual representation of the first topicobject.

In some embodiments, a portion of the visual representation of the firsttopic object comprises a selectable link, the selectable linkcorresponding to a resource object identified in association with thefirst topic object.

In some embodiments, the active audio-video conference presentation isassociated with a presentation identifier and the topic object sequenceset is associated with the presentation identifier.

In some embodiments, the computer-coded instructions are furtherconfigured to, in execution with the at least one processor, cause theapparatus to: receive a display collaborative conference presentationinterface request, wherein the display collaborative conferencepresentation interface request comprises a participating useridentifier; query a repository for agenda objects associated with theuser identifier; cause display of a collaborative conferencepresentation interface to the participating client device associatedwith the participating user identifier in association with the activeaudio-video conference presentation, wherein the collaborativeconference presentation interface comprises a rendered listing of agendaobjects returned by the query and wherein each of the agenda objects isconfigured to be selectable; identify an agenda object selectionrequest, wherein the agenda object selection request comprises an agendaobject identifier; and retrieve the topic object sequence set based onthe agenda object identifier from the repository.

In some embodiments, the shared dynamic collaborative presentationprogression interface comprises a visual representation of the topicobject sequence set. In still further embodiments, each of the topicobjects of the topic object sequence set are associated with arespective target time and the computer-coded instructions are furtherconfigured to, in execution with the at least one processor, cause theapparatus to: display a visual representation of the respective targettime in association with each topic object that is not associated with acompleted topic object identifier or an active topic object identifier.In still further embodiments, the computer-coded instructions arefurther configured to, in execution with the at least one processor,cause the apparatus to: determine an elapsed time for each completedtopic object, wherein a completed topic object is a topic objectassociated with a completed topic object identifier; display a visualrepresentation of the respective elapsed time in association with eachcompleted topic object; determine a visual emphasis element for eachcompleted topic object based at least in part on the respective targettime, wherein each visual emphasis element employs a contextuallyrelevant coloring scheme to visually indicate a comparison of theelapsed time for the completed topic object to the respective targettime of each completed topic object; and apply the determined visualemphasis elements to the visual representations of the respectiveelapsed time in association with each completed topic object.

The above summary is provided merely for purposes of summarizing someexample embodiments to provide a basic understanding of some aspects ofthe present disclosure. Accordingly, it will be appreciated that theabove-described embodiments are merely examples and should not beconstrued to narrow the scope or spirit of the present disclosure in anyway. It will be appreciated that the scope of the present disclosureencompasses many potential embodiments in addition to those heresummarized, some of which will be further described below. Otherfeatures, aspects, and advantages of the subject matter will becomeapparent from the description, the drawings, and the claims.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Having thus described certain example embodiments of the presentdisclosure in general terms above, non-limiting and non-exhaustiveembodiments of the subject disclosure will now be described withreference to the accompanying drawings which are not necessarily drawnto scale. The components illustrated in the accompanying drawings may ormay not be present in certain embodiments described herein. Someembodiments may include fewer (or more) components than those shown inthe drawings:

FIG. 1 illustrates an example collaborative presentation progressioninterface management system configured to communicate with anaudio-video conferencing interface service and two or more clientdevices in accordance with some example embodiments described herein;

FIG. 2 is a schematic block diagram of example circuitry for use in ashared dynamic collaborative presentation progression interface serverin accordance with some example embodiments described herein;

FIG. 3 is a schematic block diagram of example circuitry for use in aclient device in accordance with some example embodiments describedherein;

FIG. 4A is a flowchart illustrating example operations for generatingand managing a shared dynamic collaborative presentation progressioninterface in accordance with various aspects and embodiments of thesubject disclosure;

FIG. 4B is a signal diagram of an example data flow in accordance withvarious aspects and embodiments of the subject disclosure;

FIG. 5 is a flowchart illustrating example operations for generating andtransmitting a transition topic object sequence instructions set forupdating the shared dynamic collaborative presentation progressioninterface in accordance with various aspects and embodiments of thesubject disclosure;

FIG. 6 is a flowchart illustrating example operations for determining apresenting order and causing display of visual representations of eachof the participating user identifiers in accordance with such determinedorder in a shared dynamic collaborative presentation progressioninterface in accordance with various aspects and embodiments of thesubject disclosure;

FIG. 7 is a flowchart illustrating example operations for retrieving atopic object sequence set based on an agenda object identifieridentified in an agenda object selection request from a participatingclient device in accordance with various aspects and embodiments of thesubject disclosure;

FIG. 8 illustrates an example shared dynamic collaborative presentationprogression interface structured in accordance with some exampleembodiments described herein;

FIG. 9 illustrates an example collaborative conference presentationinterface structured in accordance with some example embodimentsdescribed herein;

FIG. 10 illustrates an example shared dynamic collaborative presentationprogression interface structured in accordance with some exampleembodiments described herein;

FIG. 11 illustrates an example shared dynamic collaborative presentationprogression interface structured in accordance with some exampleembodiments described herein;

FIG. 12 illustrates an example shared dynamic collaborative presentationprogression interface structured in accordance with some exampleembodiments described herein;

FIG. 13 illustrates an example shared dynamic collaborative presentationprogression interface structured in accordance with some exampleembodiments described herein;

FIG. 14 illustrates an example shared dynamic collaborative presentationprogression interface structured in accordance with some exampleembodiments described herein;

FIG. 15 illustrates an example shared dynamic collaborative presentationprogression interface structured in accordance with some exampleembodiments described herein; and

FIG. 16 illustrates an example shared dynamic collaborative presentationprogression interface structured in accordance with some exampleembodiments described herein.

DETAILED DESCRIPTION

One or more embodiments now will be more fully described with referenceto the accompanying drawings, wherein like reference numerals are usedto refer to like elements throughout. In the following description, forpurposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of the various embodiments. Itis evident, however, that the various embodiments can be practicedwithout these specific details (and without applying to any particularnetworked environment or standard). It should be understood that some,but not all embodiments are shown and described herein. Indeed, theembodiments may be embodied in many different forms, and accordinglythis disclosure should not be construed as limited to the embodimentsset forth herein. Rather, these embodiments are provided so that thisdisclosure will satisfy applicable legal requirements. As used herein,the description may refer to an example “apparatus.” However, elementsof the apparatus described herein may be equally applicable to theclaimed system, method, and computer program product. Accordingly, useof any such terms should not be taken to limit the spirit and scope ofembodiments of the present disclosure.

Overview

Individuals and organizations routinely use audio-video conferencingservices (e.g., Zoom®, GoToMeeting®, BlueJeans®, Webex®, Teams®, GoogleMeet®, or the like) to allow geographically-dispersed users to remotelycommunicate and collaborate within and across organizations usingindividual computing devices (e.g., laptops, desktops, smart phones,servers, and/or the like). A variety of information such as importantdecisions, action items, meeting moments, and/or the like may need tooccur during such virtual meetings and participants may desire toefficiently identify an agenda and associated responsible users for eachof the topics within the agenda before an audio-video conferencepresentation has begun and/or during an audio-video conferencepresentation. Users may also desire to identify specified time periodsfor each topic of discussion within the audio-video conferencepresentation such that audio-video conference presentation does not runlonger than required or desired.

The volume of participating users and/or presenters in an audio-videoconference presentation may cause inefficient time periods to be usedtracking down responsible users of an audio-video conferencepresentation for each topic of the agenda up for discussion. The volumeof audio-video conference presentations that each participating user(e.g., presenter of a topic within the presentation) must attend in aday, week, or month has also exploded as more presentations and meetingsare moved to the virtual space. When users are participating in such ahigh volume of virtual audio-video conference presentations, efficiencyis lowered as more users become unaware of presenter order, presentationtopic within an audio-video conference presentation, a target time foreach topic, an elapsed time for each topic, and/or responsiblepresenters for each topic before and during the audio-video conferencepresentation.

It is undesirable to require an individual participant to manuallyorganize, circulate, and maintain agendas and assigned presenters foreach topic of the agenda as audio-video conference presentations aregenerated, updated, and/or maintained. It is further undesirable torequire users to manually review the audio-video conferencepresentations after an audio-video conference presentation has beencompleted in order to find a specific time period for which a desiredtopic object was discussed in the audio-video conference presentation.Accordingly, the inventors have determined it would be desirable andadvantageous to create a collaborative presentation progressioninterface management system that is configured to programmaticallyidentify or suggest, and effectively disseminate the specified topicorder within an agenda, effectively disseminate the responsible topicpresenters and effectively disseminate presenter identifiers within theagenda, disseminate target times for each topic object, and/ordisseminate summaries of each topic object discussed after the topicobject has been completed from an audio-video conference presentation(e.g., Zoom® meeting) to a plurality of users in the collaborativepresentation progression interface management system and the pluralityof users of the audio-video conferencing interface service.

Various embodiments of the present disclosure provide apparatuses,systems, computer-implemented methods, and computer program products forgenerating and updating a shared dynamic collaborative presentationprogression interface associated with a virtual meeting and sharing theshared dynamic collaborative presentation progression interface to aplurality of users, including those users who participated in the livepresentation of the meeting and/or those users who did not. Some suchembodiments enhance meeting communication methods by reducingmiscommunication, ensuring team alignment, increasing pre-meetingaccountability, increasing efficiency within an audio-video conferencepresentation, and otherwise reducing time and cost expenditures incurredin culling and disseminating relevant information for the meeting andthe associated topic objects.

Definitions

As used herein, the term “audio-video conferencing interface service”refers to an application, program, platform, and/or service configuredfor providing virtual video and/or audio conferencing (e.g., activeaudio-video conference presentation), webinars, live chats, streamingservices, screen-sharing, and other real-time collaborative audio and/orvideo capabilities configured for display to a plurality ofparticipating client devices. Non-limiting examples of an audio-videoconferencing interface service include Zoom®, BlueJeans®, Webex®,Teams®, Google Meet®, and the like.

In some embodiments, an active audio-video conferencing interfaceservice is hosted by an “external resource” such that it is associatedwith a third-party controlled system and is configured for authenticatedcommunication with a shared dynamic collaborative presentationprogression interface system to provide audio-video conferencingfunctionality to participating client devices. An external resourceprovides functionality not provided natively by the shared dynamiccollaborative presentation progression interface system. The externalresource operates on a compiled code base or repository that is separateand distinct from that which supports the shared dynamic collaborativepresentation progression interface system. In some embodiments, theexternal resource may communicate with the shared dynamic collaborativepresentation progression interface system, and vice versa, through oneor more application program interfaces (APIs). In some embodiments, anactive audio-video conferencing interface service is hosted by theshared dynamic collaborative presentation progression interface system.

As used herein, the term “shared dynamic collaborative presentationprogression interface” refers to a user interface or sub-user interfaceof a collaborative presentation progression interface management systemthat is specially configured to enable a user to view, access, review,modify, edit, emphasize, identify, de-identify, and/or otherwise engagewith one or more topic objects of a topic object sequence set associatedwith an active audio-video conferencing interface presentation. In someembodiments, a shared dynamic collaborative presentation progressioninterface optionally comprises one or more additional topic objects, oneor more active topic objects, one or more active visual emphasiselements, one or more elapsed time objects, one or more initiate topicobject sequence set interface components, one or more topic objectprogression interface components, one or more completion indicators, oneor more annotation summaries, one or more participating useridentifiers, an upcoming presenter interface element, a rendered listingof agenda objects, a topic object sequence set, one or more respectivetarget times for each target object, and/or one or more indicators ofelapsed time (i.e., elapsed time object). For example, the shareddynamic collaborative presentation progression interface 1000 of FIG. 10is an example of a shared dynamic collaborative presentation progressioninterface comprising a selectable element for a user of a participatingclient device to input a target time at element 1020, wherein theselectable element may read “Set time”.

A shared dynamic collaborative presentation progression interface isrendered to a participating client device based on data and instructionsprovided by the collaborative presentation progression interfacemanagement system (e.g., shared dynamic collaborative presentationprogression interface server). In some embodiments, such data andinstructions are facilitated by a dedicated software application runningon the participating client device. In other embodiments, such data andinstructions are provided through a web browser running on theparticipating device. Exemplary shared dynamic collaborativepresentation progression interfaces may be rendered in any desired formincluding, but not limited to, as a mobile application for display on amobile computing device (e.g., a smartphone, table computer, etc.), awebpage or website for display on a mobile or non-mobile computingdevice via the Internet, and the like. Such a shared interface (e.g.,shared dynamic collaborative presentation progression interface) may beshared among participants and their participating client devices suchthat each participating client device can view the intended displaybased on one or more settings of the one or more participating clientdevice. Thus, even if the one or more settings for each participatingclient device render the data of the shared dynamic collaborativepresentation progression interface differently between eachparticipating client device, the contents of the data transmitted andshown on each participating client device is the same. That is, theprotocol for sending the shared interface (e.g., shared dynamiccollaborative presentation progression interface) to each participatingclient device may vary among the participating client devices as well asformat, size, etc. of the resulting interface; however, the content willgenerally be consistent among participating client devices.

In some embodiments, the shared dynamic collaborative presentationprogression interface may comprise different time data objects for eachclient device, including the one or more participating client devices.In some embodiments, the different time data objects may be based on atime zone of each of the client device, further including theparticipating client devices, such that each client device comprises atime data object associated with the time zone of the client device'slocation. In some embodiments, such a time data object may be determinedby a location service and/or GPS location. By way of non-limitingexample, Alice may be located in a time zone such as Eastern standardtime (“EST”) zone and Beth may be located in a time zone such as Pacificstandard time (“PST”) zone and the GUI of the participating clientdevice associated with Alice may be configured by the shared dynamiccollaborative presentation progression interface to include a dataobject comprising the time of day at Alice's location as 12 pm, and incontrast the GUI of the participating client device associated with Bethmay be configured by the shared dynamic collaborative presentationprogression interface to include a data object comprising the time ofday at Beth's location as 9 am. In some embodiments, the shared dynamiccollaborative presentation progression interface may configure the GUIof the one or more client devices associated with an audio-videoconference service to indicate a plurality of start time data objectsassociated with an agenda object. In some embodiments, if an agendaobject (e.g., a virtual meeting on the audio-video conference service)is associated with a start time, the shared dynamic collaborativepresentation progression interface may comprise a start time data objectindicating a start time of the agenda object and may be based on the oneor more time zones of the client devices associated with the agendaobject. By way of non-limiting example, if Alice is in the EST time zoneand Beth is in the PST time zone, and an agenda object (e.g., virtualmeeting) is set to start at 11 am central standard time (“CST”), theclient devices associated with the agenda object for one or moreparticipants in the CST time zone may comprise a start time data objectshowing 11 am as the start time, the client devices associated with theagenda object for Alice and other participants in EST zone may comprisea start time data object of 12 pm, and the client devices associatedwith the agenda object for Beth and other participants in PST maycomprise a start time data object of 10 am.

The term, “collaborative presentation progression interface managementsystem” refers to a software platform and associated hardware that isconfigured to support, maintain, and manage shared dynamic collaborativepresentation progression interface data associated with determining,tracking, identifying, highlighting, bookmarking, or otherwiseemphasizing one or more topic objects associated with an audio-videoconferencing interface service. In some embodiments, the collaborativepresentation progression interface system, or a portion thereof, is atleast partially configured to operate as a portion (e.g., a plug-in,add-on, extension, etc.) of an audio-video conferencing interfaceservice. In some embodiments, the collaborative presentation progressioninterface system, or a portion thereof, is configured to operate oncompiled code bases or repositories that are separate and distinct(e.g., a standalone collaboration server or other computing device) fromthe audio-video conferencing interface service and/or one or more clientdevices (e.g., participating client devices) associated with one or moreusers (e.g., participating users).

The term, “shared dynamic collaborative presentation progressioninterface server” refers to a software platform and associated hardwarethat is configured to generate and/or manage shared dynamiccollaborative presentation progression interface(s) in association withan audio-video conferencing interface service. The shared dynamiccollaborative presentation progression interface server is accessiblevia one or more computing devices, is configured to monitor activeaudio-video conference presentation(s), generate a shared dynamiccollaborative presentation progression interface, identify, de-identify,determine, track, highlight, and/or otherwise emphasize one or moretopic objects associated with an active audio-video conferencepresentation, and access one or more data repositories, such as a shareddynamic collaborative presentation progression interface repository. Thefunctionality of the shared dynamic collaborative presentationprogression interface server may be provided via a single server or acollection of servers having a common functionality, or thefunctionality of the shared dynamic collaborative presentationprogression interface server may be segmented among a plurality ofservers or collections of servers performing subsets of the describedfunctionality of the shared dynamic collaborative presentationprogression interface server, such as in a cloud networking environment.

A shared dynamic collaborative presentation progression interface servermay update and/or maintain a shared dynamic collaborative presentationprogression interface that provides for collaborative facilitation of anagenda and/or topic transitioning in audio-video conferencepresentations. For example, in some embodiments, the shared dynamiccollaborative presentation progression interface server is configured toenable a plurality of participating users to access, review, and/ormodify/edit a shared dynamic collaborative presentation progressioninterface at the same time. Changes and/or selections made by respectiveusers (e.g., participating users) to a shared dynamic collaborativepresentation progression interface can be automatically stored/saved andsynced between all users in real-time. For example, a firstparticipating user may select and/or otherwise activate an initiatetopic object sequence set interface component (e.g., click a “StartMeeting” button) or an object progression interface component (e.g.,click a “Next Topic” button) in association with a shared dynamiccollaborative presentation progression interface, thereby indicating aninitiation of a first topic object or progression/transition of topicobjects in a topic object sequence set and all participating users maybe able to view the updated shared dynamic collaborative presentationprogression interface in real time.

The term “shared dynamic collaborative presentation progressioninterface repository” refers to a location, such as a database stored ona memory device, which is accessible by one or more computing devicesfor retrieval and storage of data associated with shared dynamiccollaborative presentation progression interface(s). For example, theshared dynamic collaborative presentation progression interfacerepository includes one or more of shared dynamic collaborativepresentation progression interface(s), topic object identifier(s), useridentifier(s), participating user identifier(s), presentationidentifier(s), agenda object identifier(s), and/or the like. The shareddynamic collaborative presentation progression interface repository maybe a dedicated device and/or a part of a larger repository. The shareddynamic collaborative presentation progression interface repository maybe dynamically updated or be static. In some embodiments, the shareddynamic collaborative presentation progression interface repository isencrypted in order to limit unauthorized access of such shared dynamiccollaborative presentation progression interface data.

The terms “data,” “content,” “digital content,” “digital contentobject,” “signal”, “information,” and similar terms may be usedinterchangeably to refer to data capable of being transmitted, received,and/or stored in accordance with embodiments of the present invention.Thus, use of any such terms should not be taken to limit the spirit andscope of embodiments of the present invention. Further, where acomputing device is described herein to receive data from anothercomputing device, it will be appreciated that the data may be receiveddirectly from another computing device or may be received indirectly viaone or more intermediary computing devices, such as, for example, one ormore servers, relays, routers, network access points, base stations,hosts, and/or the like, sometimes referred to herein as a “network.”Similarly, where a computing device is described herein to send data toanother computing device, it will be appreciated that the data may betransmitted directly to another computing device or may be transmittedindirectly via one or more intermediary computing devices, such as, forexample, one or more servers, relays, routers, network access points,base stations, hosts, and/or the like.

As used herein, the term “client device”, “computing device”, “userdevice”, and the like may be used interchangeably to refer to computerhardware that is configured (either physically or by the execution ofsoftware) to access one or more of an application, service, orrepository made available by a server (e.g., apparatus of the presentdisclosure) and, among various other functions, is configured todirectly, or indirectly, transmit and receive data. The server is often(but not always) on another computer system, in which case the clientdevice accesses the service by way of a network. Example client devicesinclude, without limitation, smart phones, tablet computers, laptopcomputers, wearable devices (e.g., integrated within watches orsmartwatches, eyewear, helmets, hats, clothing, earpieces with wirelessconnectivity, and the like), personal computers, desktop computers,enterprise computers, the like, and any other computing devices known toone skilled in the art in light of the present disclosure. In someembodiments, a client device is associated with a user. In someembodiments, an association is created by a client device transmittingauthentication information associated with the user for the selectedactive audio-video conference presentation to the audio-videoconferencing interface service and/or a collaborative presentationprogression interface management system.

As used herein, the term “participating client device” or “participatingclient devices” of an active audio-video conference presentation refersto a client device associated with a user identifier identified asdisposed in a real-time communicative relation with the live streampresentation of the active audio-video conference presentation.

As used herein, the term “topic object identifier” refers to one or moreitems of data by which a topic or portion of an active audio-videoconference presentation may be identified within a collaborativepresentation progression interface management system. For example, atopic object identifier may comprise text string(s), numericalcharacter(s), alphabetical character(s), alphanumeric code(s), ASCIIcharacter(s), a pointer, an IP address, a MAC address, a memory address,other unique identifier, or a combination thereof.

As used herein, the term “topic object progression interface component”refers to a user interface component, sub-user interface component, ormodal that is rendered to a shared dynamic collaborative presentationprogression interface and is specially configured to enable aparticipating user to indicate an intention to progress to another topicobject in a topic object sequence set associated with a correspondingactive audio-video conference presentation. In some embodiments, aparticipating user selects, activates, or otherwise interacts with aspecific actuator button or interface element rendered to the shareddynamic collaborative presentation progression interface on a visualdisplay of the participating client device (e.g., a user clicking on a“Next Topic” icon during an active audio-video conference presentation),thereby indicating the current topic object is completed and a new topicobject should be identified as active.

As used herein, the term “agenda object identifier” refers to one ormore items of data by which one or more topics of an active audio-videoconference presentation may be identified and ordered within acollaborative presentation progression interface management system. Forexample, an agenda object identifier may comprise text string(s),numerical character(s), alphabetical character(s), alphanumeric code(s),ASCII character(s), a pointer, an IP address, a MAC address, a memoryaddress, other unique identifier, or a combination thereof.

As used herein, the term “completed topic object identifier” refers toone or more items of data by which a topic or portion of an activeaudio-video conference presentation which has been completed and may beidentified within a collaborative presentation progression interfacemanagement system. For example, a presentation identifier may comprisetext string(s), numerical character(s), alphabetical character(s),alphanumeric code(s), ASCII character(s), a pointer, an IP address, aMAC address, a memory address, other unique identifier, or a combinationthereof.

As used herein, the term “completed topic object” refers to one or moreelectronically managed data representing a completed topic, wherein thecompleted topic is associated with a completed topic object identifier.The completed topic object is a data representation of a completed topicthat has, at a previous point in time, been identified by thecollaborative presentation progression interface management system(e.g., a shared dynamic collaborative presentation progression interfaceserver) as an active topic object and was subsequently de-identified asthe active topic object. For example, in response to monitoring anactive audio-video conference presentation and receiving indications ofuser interaction(s) of one or more participating users with a shareddynamic collaborative presentation topic progression interface renderedto respective displays of participating client devices, the shareddynamic collaborative presentation progression interface serveridentifies a topic object as an active topic object (e.g., associatingthe selected topic object with an active topic object identifier) andsubsequently de-identifies the topic object as an active topic object(e.g., dissociating the selected topic object from the active topicobject identifier) and identifies the topic object as a completed topicobject (e.g., associating the selected topic object with a completedtopic object identifier). The one or more topic objects may beassociated with at least one of a topic object sequence set and/or atransition topic object sequence instruction set to determine a sequenceor order in which the topic objects may be completed to render one ormore completed topic objects. The completed topic object(s) iscorrelated to a shared dynamic collaborative presentation interface. Ina non-limiting example context, a completed topic object refers toelectronically managed data that represents a topic object of a topicobject sequence set associated with an active video-conferencepresentation, wherein the completed topic object indicates one or moretopics previously completed by one or more presenters of the activeaudio-video conference presentation.

As used herein, the term “visual emphasis element” refers to a visualrepresentation in a user interface configured to visually conveyinformation to the user. For example, in some embodiments, a visualemphasis element visually compares an elapsed time of a completed topicobject to a target time associated with the completed topic object. Inanother example, in some embodiments, a visual emphasis element visuallycompares an elapsed time of an active topic object to a target timeassociated with the active topic object. In yet another example, in someembodiments, an “active visual emphasis element” visually identifies theactive topic object of the topic object sequence set (e.g., as thecurrent topic object as compared to completed topic objects and/orupcoming topic objects) associated with the shared dynamic collaborativepresentation progression interface.

To provide context, a visual emphasis element may be determined usingvarious embodiments described herein, such as identifying orde-identifying an active topic object based on an analysis of associatedidentifiers or performing an analysis of an elapsed time and a targettime. Examples of visual representation associated with a visualemphasis element include, but are not limited to, an icon, text, and/orbackground displayed in a user interface (e.g., shared dynamiccollaborative presentation progression interface). In some embodiments,the visual emphasis element may comprise a contextually relevantcoloring scheme which may identify one or more colors associated withthe content of the configured data object as relevant to the content inorder to configure said data object accordingly (e.g., the highimportance topic objects may be configured to a red color to highlightsaid high importance). For example, in a non-limiting illustration, avisual emphasis element for elapsed time associated with a completed oractive topic object may comprise text in orange, an orange icon (e.g.,an arrow or other indication of overtime), and/or an orange backgroundshading to indicate that the elapsed time associated with thecorresponding topic object may be overtime. In a further example, avisual emphasis element for elapsed time associated with a completed oractive topic object may comprise text in green, a green icon (e.g., athumbs up, a checkmark, or other indication of sufficient time, etc.),and/or a green background shading to indicate that the elapsed timeassociated with the corresponding topic object is adequate, sufficient,or otherwise on target with the target time. In another example, anactive visual emphasis element emphasizes and/or otherwise indicates asimportant a configured data object (e.g., emphasizing as an active topicobject in association with the visual representation of a topic objectrendered on a shared dynamic collaborative presentation progressioninterface). Additional examples of visual emphasis elements includeemphasizing an icon or text displayed on a user interface (e.g.,coloring scheme, highlighted, bolded, italicized, enlarged, shaded,flashing, pulsing, changing font, changing in size, etc.). Additionalexamples of visual emphasis elements include numerous embodimentsdescribed herein and would be understood to include any other visualindicators in light of the present disclosure.

As used herein, the term “completion indicator” refers to a renderableindicator displayed to a shared dynamic collaborative presentationprogression interface, the completion indicator associated with one ormore completed topic objects and the one or more completed topic objectidentifiers. In some embodiments, the completion indicator is selectedand/or generated from a plurality of completion indicators, eachcompletion indicator associated with a different format, size,placement, type, color, highlight, tag, graphic, figure, and/or type. Insome embodiments, the completion indicator is rendered in a position orlocation of the shared dynamic collaborative presentation progressioninterface such that it is indicative of a completed topic object in atopic object sequence set.

As used herein, the term “user identifier” refers to refers to one ormore items of data by which a user may be identified within a shareddynamic collaborative presentation progression interface system. Forexample, a user identifier may comprise text string(s), numericalcharacter(s), alphabetical character(s), alphanumeric code(s), ASCIIcharacter(s), a pointer, an IP address, a MAC address, a memory address,other unique identifier, or a combination thereof.

As used herein, the term “presentation identifier” refers to refers toone or more items of data by which an active audio-video conferencepresentation may be identified within a shared dynamic collaborativepresentation progression interface system. For example, a presentationidentifier may comprise text string(s), numerical character(s),alphabetical character(s), alphanumeric code(s), ASCII character(s), apointer, an IP address, a MAC address, a memory address, other uniqueidentifier, or a combination thereof.

As used herein, the term “agenda object selection request” refers to anelectronically generated digital object that is created by or otherwiseoriginates from a computing device (e.g., a participating client device)indicating that a user has provided an input comprising a request toselect an agenda object identifier in association with a collaborativeconference presentation interface. In some embodiments, an agenda objectselection request is represented via a temporary code that is generatedby and/or transmitted from a computing device (e.g., participatingclient device) to a collaborative presentation progression interfacemanagement system (e.g., shared dynamic collaborative presentationprogression interface server) as an indication that a participatingclient device has made the request. In some embodiments, the selectionof such an agenda object identifier may comprise a request to present,highlight, tag, bookmark, illustrate, and/or otherwise emphasize theagenda object identifier on a shared dynamic collaborative presentationprogression interface. In some embodiments, the selection of such anagenda object identifier may comprise a request to edit the agendaobject identifier using text, format, size, style, content, and/or othersuch data of the agenda object identifier. The selected content of theagenda object selection request may be shared among and accessed byparticipating client devices on a shared dynamic collaborativepresentation progression interface in association with an activeaudio-video conference presentation. In some embodiments, the agendaobject selection request is associated with a variety of metadata suchas one or more of a participating user identifier, an agenda objectidentifier, one or more topic object identifiers, one or more topicobject sequence sets, and/or other data for use in managing an agendaobject selection request.

As used herein, the term “collaborative conference presentationinterface” refers to a user interface, sub-user interface, or modal thatis rendered on a shared dynamic collaborative presentation progressioninterface and is specially configured to display a rendering of one ormore agenda objects for the active audio-video conference presentation,one or more of users of participating client devices, and one or moredata representing the active audio-video conference presentation. Forinstance, the collaborative conference presentation interface can beused to configure one or more agenda objects by one or moreparticipating client devices to be associated with an active audio-videoconference presentation.

As used herein, the term “display collaborative conference presentationinterface request” refers to an electronically generated digital objectcreated by a computing device (e.g., a participating client device)indicating that a user has provided an input comprising a request toaccess and/or display a collaborative conference presentation interfaceto a shared dynamic collaborative presentation progression interfaceassociated with an active audio-video conference presentation. In someembodiments, a display collaborative conference presentation interfacerequest is represented via a temporary code that is generated by and/ortransmitted from a computing device (e.g., participating client device)to a collaborative presentation progression interface management system(e.g., shared dynamic collaborative presentation progression interfaceserver) as an indication that a participating client device has made therequest. In some embodiments, the display collaborative conferencepresentation interface request is associated with a variety of metadatasuch as one or more of a participating user identifier, a presentationidentifier, and/or other data for use in managing a displaycollaborative conference presentation interface request.

As used herein, the term “active topic object identifier” refers to oneor more items of data by which one or more active topics (e.g., currenttopic(s) of discussion) of an active audio-video conference presentationmay be identified within a collaborative presentation progressioninterface management system. For example, an active topic objectidentifier may comprise text string(s), numerical character(s),alphabetical character(s), alphanumeric code(s), ASCII character(s), apointer, an IP address, a MAC address, a memory address, other uniqueidentifier, or a combination thereof.

As used herein, the term “active topic object” refers to one or moreelectronically managed data representing a current topic object, whereinthe current topic is associated with an active topic object identifier.The active topic object is a data representation of the active topicthat is identified by the collaborative presentation progressioninterface management system (e.g., a shared dynamic collaborativepresentation progression interface server) in response to monitoring andidentification of one or more topic objects to determine at least anactive topic of one or more data objects associated with an agenda topicobject identifier and/or a topic object sequence set. For example, inresponse to monitoring an active audio-video conference presentation andreceiving indications of user interaction(s) of one or moreparticipating users with a shared dynamic collaborative presentationtopic progression interface rendered to respective displays ofparticipating client devices, a shared dynamic collaborativepresentation progression interface server identifies one or more topicscurrently being discussed in association with the active audio-videoconference presentation The one or more topic objects may be associatedwith at least one of a topic object sequence set and/or a transitiontopic object sequence instruction set to determine a sequence or orderin which the topic objects may be identified and/or rendered as anactive topic object. The active topic object is correlated to a shareddynamic collaborative presentation progression interface. In anon-limiting example context, an active topic object refers toelectronically managed data that represents the current topic of theassociated active video-conference presentation comprised within a topicobject sequence set to indicate one or more topics currently discussedby one or more presenters of the active audio-video conferencepresentation.

As used herein, the term “facilitation topic object” refers to one ormore electronically managed data representing one or more specifiedtemplates (i.e., facilitation templates) of topic object(s), wherein atemplate of topic object(s) may comprise one or more topic objects in aspecified order and/or specified types of topic objects. Thefacilitation topic object is a data representation of the one or moretopic objects within a specified template that is identified by thecollaborative presentation progression interface management system(e.g., a shared dynamic collaborative presentation progression interfaceserver) in response to monitoring and identification of one or moretopic objects in a specified template of topic objects. The facilitationtopic object may be selected by a selectable link on the shared dynamiccollaborative presentation progression interface. The collaborativepresentation progression interface management system (e.g., a shareddynamic collaborative presentation progression interface server) mayidentify the facilitation topic object selected by one or more users ofthe shared dynamic collaborative presentation progression interface(e.g., a shared dynamic collaborative presentation progression interfaceserver) and, in response to identifying the selected facilitation topicobject, may identify and/or select one or more first topic objects to bethe active topic object and/or a template of topic objects comprisingone or more non-active topic objects (e.g., future active objects in atopic object sequence set determined by the facilitation topic object).For example, in response to monitoring an active audio-video conferencepresentation and receiving indications of user interaction(s) of one ormore participating users with a shared dynamic collaborativepresentation topic progression interface rendered to respective displaysof participating client devices, a shared dynamic collaborativepresentation progression interface server identifies one or more topicsin a specified template of a facilitation topic object selected by oneor more users. By way of non-limiting example, and in some embodiments,the specified template of the facilitation topic object may comprise aplurality of topic objects associated with an introduction template foran audio-visual conference presentation, where each topic object of theintroduction template may comprise a participating user identifier toidentify one or more participating user identifiers who will introducethemselves in the audio-visual conference presentation. By way of anon-limiting example, in further embodiments, the introduction templatemay further comprise a randomizer of the topic objects (e.g., the one ormore participating user identifiers may be in a randomized order). Byway of non-limiting example, and in some embodiments, an introductiontemplate of the facilitation topic object may comprise an orderassociated with an order of those participating users (e.g.,participating user devices) based on the order in which they joined theaudio-video conference presentation and/or accessed the shared dynamiccollaborative presentation progression interface server. In someembodiments, the facilitation topic object may comprise one or moreprompts for each topic object, such as a prompt asking one or morequestions to each participating user of the participating useridentifiers identified in the facilitation template of the facilitationtopic object (e.g., a user associated with an active topic object of thefacilitation template may be prompted by the shared dynamiccollaborative presentation progression interface server/shared dynamiccollaborative presentation progression interface to say their name,occupation, age, city/state of residence, educational institutionattended, and/or any other introductory prompt known in the art).

In some embodiments, the randomizer of the topic objects may further beconfigured to randomize one or more topic objects associated with one ormore specified participating user identifiers. By way of non-limitingexample, the shared dynamic collaborative presentation progressioninterface server may determine whether one or more participating usersare present and/or signed into the shared dynamic collaborativepresentation progression interface (e.g., signed in to attend theaudio-video conference presentation) by matching the participating useridentifiers of each of the topic objects in the topic object sequenceset to the one or more participating user identifiers present in theshared dynamic collaborative presentation progression interface (e.g.,signed into the audio-video conference presentation). In someembodiments, and by way of further example, if any of the participatinguser identifiers which are determined by the shared dynamiccollaborative presentation progression interface server as not inattendance to the audio-video conference presentation, the shareddynamic collaborative presentation progression interface server mayrandomize the topic objects of the topic object sequence set associatedwith the absent participating users to the end of the topic objectsequence set. By way of non-limiting example, if Alice is late to theaudio-video conference presentation and is assigned to the second topicobject of the topic object sequence set and Cheri is also late to theaudio-video conference presentation and is assigned to the fourth topicobject of the topic object sequence set, then the shared dynamiccollaborative presentation progression interface server may randomizethe second topic object and the fourth topic object at the end of thetopic object sequence set such that the fourth topic object isre-assigned to the sixth topic object and the second topic object isreassigned to the seventh topic object of the seven topic objects.

As used herein, the term “participating user identifier” refers to oneor more items of data by which one or participants of an activeaudio-video conference presentation may be identified within acollaborative presentation progression interface management system. Forexample, a participating user identifier may comprise text string(s),numerical character(s), alphabetical character(s), alphanumeric code(s),ASCII character(s), a pointer, an IP address, a MAC address, a memoryaddress, other unique identifier, or a combination thereof.

The term “topic object sequence set” refers to a set of data objectscorresponding to a plurality of topic objects and the specified order ofthe topic objects based upon one or more indicators by a user (e.g., aselection by one or more users based on user interaction(s) with ashared dynamic collaborative presentation topic progression interface,wherein one or more users may select and/or input an order of topicobjects for an audio-video conference presentation). For example, inresponse to monitoring an active audio-video conference presentation andreceiving indications from user interaction(s) of one or moreparticipating users with a shared dynamic collaborative presentationtopic progression interface rendered to respective displays ofparticipating client devices, a shared dynamic collaborativepresentation progression interface server may identify one or moretopics to be discussed in association with the active audio-videoconference presentation. In some embodiments, the topic object sequenceset may be a set of data objects randomly selected by the shared dynamiccollaborative presentation progression interface server. For example,the shared dynamic collaborative presentation progression interfaceserver may, in response to one or more user indication(s), the shareddynamic collaborative presentation progression interface server maymonitor one or more inputs by a user selecting a randomizer (e.g., suchas a button labeled “randomize”) for the topic object sequence set andgenerate the topic object sequence set using a randomizer method. Suchrandomizers methods may comprise at least one of a random numbergenerator or a pseudo-random number generator.

The term “identify random presentation order event” refers to anelectrically generated digital object that is generated and/or createdby a computing device (e.g., a participating client device), based onone or more user interaction(s) with the shared dynamic collaborativepresentation topic progression interface, and transmitted to the shareddynamic collaborative presentation progression interface system, theidentify random presentation order event indicating a request toidentify and/or generate a random presentation order associated with theaudio-video conference presentation. In some embodiments, the identifyrandom presentation order event is associated with randomizing an orderof participating user identifiers for presenting one topic object and/ora plurality of topic objects. In some embodiments, the identify randompresentation order event is associated with randomizing an order oftopic objects associated with the audio-video conference presentation.For example, a user of the shared dynamic collaborative presentationprogression interface system interacting with the shared dynamiccollaborative presentation topic progression interface via aparticipating client device may select a button configured on a GUI ofthe shared dynamic collaborative presentation progression interface,such as a button configured to read, “Randomize” or “Random Order” (suchas depicted by the button 1410 of FIG. 14 , which generates a temporarycode and/or instructions that are transmitted to and detected by theshared dynamic collaborative presentation progression interface system,indicating the user's request to randomize the participating useridentifiers and/or topic objects associated with the audio-videoconference presentation. In some embodiments, the shared dynamiccollaborative presentation progression interface server determines arandomized presenting order (e.g., of topic objects and/or participatinguser identifiers) using one or more randomizer methods. In someembodiments, such randomizer methods comprise at least one of a randomnumber generator or a pseudo-random number generator. In someembodiments, the entire random presenting order is defined at once.Additionally or alternatively, a randomizer method is used anew at eachposition.

The term “initiate topic object sequent set event” refers to anelectrically generated digital object that is generated and/or createdby a computing device (e.g., a participating client device), based onone or more user interaction(s) with the shared dynamic collaborativepresentation topic progression interface, and transmitted to the shareddynamic collaborative presentation progression interface system, theinitiate topic object sequence event indicating a request to start,commence, or otherwise initiate the topic object sequence set associatedwith the shared dynamic collaborative presentation topic progressioninterface and the audio-video conference presentation. For example, auser of the shared dynamic collaborative presentation progressioninterface system interacting with the shared dynamic collaborativepresentation topic progression interface via a participating clientdevice may select a button configured on a GUI of the shared dynamiccollaborative presentation progression interface, such as a buttonconfigured to read, “Start meeting” or “Get Started.” (such as depictedby the button [Reference Numeral] of FIG. 7 or FIG. 10 ), whichgenerates a temporary code and/or instructions that are transmitted toand detected by the shared dynamic collaborative presentationprogression interface system, indicating the user's request to start theflow of the topic object sequence set, such as identify a first topicobject of the topic object sequence set as the active topic object. Insome embodiments, the initiate topic object sequence set event isassociated with a request to start the audio-video conferencepresentation. For example, in response to detecting an initiate topicobject sequence set event that is associated with a request to start theaudio-video conference presentation, in addition to initiating the topicobject sequence set event, in some embodiments, the shared dynamiccollaborative presentation progression interface system furthertransmits such event (or generates a new event based on detection of theinitiate topic object sequence set event) to the audio-videoconferencing interface service. Additionally or alternatively, in someembodiments, upon detection of the initiate topic object sequence setevent, the shared dynamic collaborative presentation progressioninterface system initiates one or more timers associated with the topicobject sequence set event and/or the audio-video conferencepresentation.

The term “topic object progression event” refers to an electronicallygenerated digital object that is generated and/or created by a computingdevice (e.g., a participating client device), based on one or more userinteraction(s) with the shared dynamic collaborative presentation topicprogression interface, and transmitted to the shared dynamiccollaboration presentation progression interface system, the topicobject progression event indicating a request to identify and/orgenerate a topic object progression associated with the audio-videoconference presentation. In some embodiments, the topic objectprogression event is associated with an ordering of the topic objectsassociated with the audio-video conference presentation. For example, auser of the shared dynamic collaborative presentation progressioninterface system interacting with the shared dynamic collaborativepresentation topic progression interface via a participating clientdevice may select a button configured on a GUI, such as a buttonconfigured to read, “Next Topic” (such as depicted by 1120 of FIG. 11 ,which generates a temporary code and/or instructions that aretransmitted to and detected by the shared dynamic collaborativepresentation progression interface system, indicating the user's requestto proceed to a different topic than the current topic (e.g., activetopic object) in the audio-video conference presentation.

The term “transition topic object sequence instructions set” refers toinstructions provided by the collaborative presentation progressioninterface management system (e.g., shared dynamic collaborativepresentation progression interface server) and transmitted to one ormore participating client devices to render a shared dynamiccollaborative presentation progression interface. For example, thetransition topic object sequence instruction set may be transmitted toone or more participating client devices for updating the shared dynamiccollaborative presentation progression interface during the progressionof the agenda for an audio-video conference presentation, such as byfollowing the topic object sequence set as it progresses through one ormore active topic objects and/or one or more completed topic objects.The transition topic object sequence set may update the one or moreconfigured GUIs of the one or more participating client devicescomprising the shared dynamic collaborative presentation progressioninterface to update the shared dynamic collaborative presentationprogression interface as each topic of the topic object sequence set issatisfied (e.g., completed) and/or activated (e.g., currently discussedand/or selected for discussion).

The term “upcoming presenter notification element” refers to a visualrepresentation of one or more users in a user interface configured tovisually convey information of the one or more users to a user of acomputing device associated with the collaborative presentationprogression interface management system (e.g., shared dynamiccollaborative presentation progression interface server). For example,in some embodiments, an upcoming presenter notification element mayvisually indicate an order of presenters (e.g., participating users ofthe participating client devices) of the audio-video conferencepresentation, which may include one or more identifying data objectsassociated with the users (e.g., names, usernames, email addresses,phone numbers, icons, pictures, etc., associated with the one or moreparticipating users of the participating client devices). For example, alist of users and/or identifying data objects associated with the users1515, 1520, and 1525 of FIG. 15 are examples of an upcoming presenternotification element.

The term “display upcoming presenter notification event” refers to datagenerated based on the topic object sequence set and one or morecompleted topic objects, one or more active topic objects, and/or one ormore upcoming topic objects (e.g., not-yet active topic objects which,according to the topic object sequence set, are upcoming on the list oftopics within the topic object sequence set), wherein the displayupcoming presenter notification event may comprise instructionstransmitted to one or more participating client devices associated withone or more users associated with a next topic object or a plurality oftopic objects on the topic object sequence set to indicate to the usersthat the associated topic for each user is upcoming and/or next. Forexample, in some embodiments, the display upcoming presenternotification event may comprise a GUI configured to indicate to thespecific user of the participating client device that the topic objectassociated with the user is upcoming in the topic object sequence set.For instance, the display upcoming presenter notification event may beindicated on a configured GUI by a pop-up window, a graphic, anelectronically-generated sound, a flash of light, and other suchelectronically generated indicating instances. For example, a configuredGUI of the participating client device may comprise an indication to theuser, such as elements 1515, 1520, and 1525 of FIG. 15 , which is anexample of a display upcoming presenter notification event.

The term “elapsed time object” refers to a visual representation in auser interface (e.g., shared dynamic collaborative presentationprogression interface) to visually convey information to the user. Forexample, in some embodiments, an elapsed time object visually indicatesan elapsed time (e.g., time already spent or time already taken todiscuss, show, and/or explain a topic associated with one or morecompleted topic objects and/or one or more active topic objects) of oneor more topic objects, such as one or more completed topic objects whichhave been discussed and/or completed. In some embodiments, an elapsedtime object may visually indicate a current time spent and/or time takento discuss an active topic object of the audio-video conferencepresentation. In some embodiments, the elapsed time object may comprisea target time for the topic object to be discussed, wherein the elapsedtime may comprise time data beyond (e.g., over) the target timeindicating the time taken to discuss the associated topic object wentlonger than the target time of the associated topic object. For example,the time and/or clock 1405 of FIG. 14 and 1505 of FIG. 15 are examplesof an elapsed time objects. For example, the time and/or clock of 1210and/or 1215 of FIG. 12 are examples of a target time.

The terms “computer-readable storage medium” refers to a non-transitory,physical or tangible storage medium (e.g., volatile or non-volatilememory), which may be differentiated from a “computer-readabletransmission medium,” which refers to an electromagnetic signal. Such amedium can take many forms, including, but not limited to anon-transitory computer-readable storage medium (e.g., non-volatilemedia, volatile media), and transmission media. Transmission mediainclude, for example, coaxial cables, copper wire, fiber optic cables,and carrier waves that travel through space without wires or cables,such as acoustic waves and electromagnetic waves, including radio,optical, infrared waves, or the like. Signals include man-made, ornaturally occurring, transient variations in amplitude, frequency,phase, polarization or other physical properties transmitted through thetransmission media.

Examples of non-transitory computer-readable media include a magneticcomputer readable medium (e.g., a floppy disk, hard disk, magnetic tape,any other magnetic medium), an optical computer readable medium (e.g., acompact disc read only memory (CD-ROM), a digital versatile disc (DVD),a Blu-Ray disc, or the like), a random access memory (RAM), aprogrammable read only memory (PROM), an erasable programmable read onlymemory (EPROM), a FLASH-EPROM, or any other non-transitory medium fromwhich a computer can read. The term computer-readable storage medium isused herein to refer to any computer-readable medium except transmissionmedia. However, it will be appreciated that where embodiments aredescribed to use a computer-readable storage medium, other types ofcomputer-readable mediums can be substituted for or used in addition tothe computer-readable storage medium in alternative embodiments.

The terms “application,” “software application,” “app,” “product,”“service” or similar terms refer to a computer program or group ofcomputer programs designed to perform coordinated functions, tasks, oractivities for the benefit of a user or group of users. A softwareapplication can run on a server or group of servers (e.g., a physical orvirtual servers in a cloud-based computing environment). In certainembodiments, an application is designed for use by and interaction withone or more local, networked or remote computing devices, such as, butnot limited to, client devices. Non-limiting examples of an applicationcomprise workflow engines, service desk incident management, teamcollaboration suites, cloud services, word processors, spreadsheets,accounting applications, web browsers, email clients, media players,file viewers, videogames, audio-video conferencing, and photo/videoeditors. In some embodiments, an application is a cloud product.

The term “comprising” means including but not limited to and should beinterpreted in the manner it is typically used in the patent context.Use of broader terms such as comprises, includes, and having should beunderstood to provide support for narrower terms such as consisting of,consisting essentially of, and comprised substantially of.

The phrases “in one embodiment,” “according to one embodiment,” and thelike generally mean that the particular feature, structure, orcharacteristic following the phrase may be included in the at least oneembodiment of the present invention and may be included in more than oneembodiment of the present invention (importantly, such phrases do notnecessarily refer to the same embodiment).

The terms “illustrative,” “example,” “exemplary” and the like are usedherein to mean “serving as an example, instance, or illustration” withno indication of quality level. Any implementation described herein as“exemplary” is not necessarily to be construed as preferred oradvantageous over other implementations.

The terms “about,” “approximately,” or the like, when used with anumber, may mean that specific number, or alternatively, a range inproximity to the specific number, as understood by persons of skill inthe art field.

If the specification states a component or feature “may,” “can,”“could,” “should,” “would,” “preferably,” “possibly,” “typically,”“optionally,” “for example,” “often,” or “might” (or other suchlanguage) be included or have a characteristic, that particularcomponent or feature is not required to be included or to have thecharacteristic. Such component or feature may be optionally included insome embodiments, or it may be excluded.

The term “set” refers to a collection of one or more items.

The term “plurality” refers to two or more items.

The term “or” is used herein in both the alternative and conjunctivesense, unless otherwise indicated.

Having set forth a series of definitions called-upon throughout thisapplication, an example system architecture and example apparatus isdescribed below for implementing example embodiments and features of thepresent disclosure.

Example System Architecture

Methods, apparatuses, systems, and computer program products of thepresent disclosure may be embodied by any of a variety of computingdevices. For example, the method, apparatus, system, and computerprogram product of an example embodiment may be embodied by a networkeddevice, such as a server or other network entity, configured tocommunicate with one or more devices, such as one or more clientdevices. Additionally, or alternatively, the computing device mayinclude fixed computing devices, such as a personal computer or acomputer workstation. Still further, example embodiments may be embodiedby any of a variety of mobile devices, such as a portable digitalassistant (PDA), mobile telephone, smartphone, laptop computer, tabletcomputer, wearable, or any combination of the aforementioned devices.

With reference to FIG. 1 , an example computing system 100 within whichsome embodiments of the present disclosure operate is illustrated. Inparticular, FIG. 1 illustrates an example collaborative presentationprogression interface management system 200 configured to communicatewith an audio-video conferencing interface service and/or two or moreclient devices 101A-101N in accordance with some example embodimentsdescribed herein. Users may access a collaborative presentationprogression interface management system 200 via a communications network102 using one or more of client devices 101A-101N. Collaborativepresentation progression interface management system 200 may comprise ashared dynamic collaborative presentation progression interface server210 in communication with at least one repository, such as shareddynamic collaborative presentation progression interface repository 215.Such repository(ies) may be hosted by the shared dynamic collaborativepresentation progression interface server 210 or otherwise hosted bydevices in communication with the shared dynamic collaborativepresentation progression interface server 210. The collaborativepresentation progression interface management system 200 is, in someembodiments, able to generate a shared dynamic collaborativepresentation progression interface in association with an audio-videoconferencing interface service, as will be described below.

Shared dynamic collaborative presentation progression interface server210 may include circuitry, networked processors, or the like configuredto perform some or all of the shared dynamic collaborative presentationprogression interface server-based processes described herein (e.g.,generate and/or transmit commands and instructions for rendering ashared dynamic collaborative presentation progression interface toclient devices 101A-101N, using data from, for example, shared dynamiccollaborative presentation progression interface repository 215), andmay be any suitable network server and/or other type of processingdevice. In this regard, the shared dynamic collaborative presentationprogression interface server 210 may be embodied by any of a variety ofdevices, for example, the shared dynamic collaborative presentationprogression interface server 210 may be embodied as a computer or aplurality of computers. For example, shared dynamic collaborativepresentation progression interface server 210 may be configured toreceive/transmit data and may include any of a variety of fixedterminals, such as a server, desktop, or kiosk, or it may comprise anyof a variety of mobile terminals, such as a portable digital assistant(PDA), mobile telephone, smartphone, laptop computer, tablet computer,or in some embodiments, a peripheral device that connects to one or morefixed or mobile terminals. Example embodiments contemplated herein mayhave various form factors and designs but will nevertheless include atleast the components illustrated in FIG. 2 and described in connectiontherewith. In some embodiments, shared dynamic collaborativepresentation progression interface server 210 may be located remotelyfrom the shared dynamic collaborative presentation progression interfacerepository 215, although in other embodiments, the shared dynamiccollaborative presentation progression interface server 210 may comprisethe shared dynamic collaborative presentation progression interfacerepository 215. The shared dynamic collaborative presentationprogression interface server 210 may, in some embodiments, compriseseveral servers or computing devices performing interconnected and/ordistributed functions. Despite the many arrangements contemplatedherein, shared dynamic collaborative presentation progression interfaceserver 210 is shown and described herein as a single computing device toavoid unnecessarily overcomplicating the disclosure.

Shared dynamic collaborative presentation progression interface server210 can communicate with one or more client devices 101A-101N and/or anaudio-video conferencing interface service 105 via communicationsnetwork 102. Communications network 102 may include any one or morewired and/or wireless communication networks including, for example, awired or wireless local area network (LAN), personal area network (PAN),metropolitan area network (MAN), wide area network (WAN), or the like,as well as any hardware, software and/or firmware required forimplementing the one or more networks (e.g., network routers, switches,hubs, etc.). For example, communications network 102 may include acellular telephone, mobile broadband, long term evolution (LTE),GSM/EDGE, UMTS/HSPA, IEEE 802.11, IEEE 802.16, IEEE 802.20, Wi-Fi,dial-up, and/or WiMAX network. Furthermore, the communications network102 may include a public network, such as the Internet, a privatenetwork, such as an intranet, or combinations thereof, and may utilize avariety of networking protocols now available or later developedincluding, but not limited to TCP/IP based networking protocols. Forinstance, the networking protocol may be customized to suit the needs ofthe collaborative contextual summary interface management system 200.

Shared dynamic collaborative presentation progression interfacerepository 215 may be stored by any suitable storage device configuredto store some or all of the information described herein (e.g., memory201 of the shared dynamic collaborative presentation progressioninterface server 210 or a separate memory system separate from theshared dynamic collaborative presentation progression interface server210, such as one or more database systems, backend data servers, networkdatabases, cloud storage devices, or the like provided by another device(e.g., online application or 3rd party provider), such as a NetworkAttached Storage (NAS) device or devices, or as a separate databaseserver or servers). Shared dynamic collaborative presentationprogression interface repository 215 may comprise data received from thecollaborative presentation progression interface server 210 (e.g., via amemory 201 and/or processor(s) 202) and/or a client device 101A-101N,and the corresponding storage device may thus store this data. Shareddynamic collaborative presentation progression interface repository 215includes information accessed and stored by the Shared dynamiccollaborative presentation progression interface server 210 tofacilitate the operations of the collaborative presentation progressioninterface management system 200. As such, Shared dynamic collaborativepresentation progression interface repository 215 may include, forexample, without limitation, user identifier(s), elapsed timeidentifier(s), target time identifier(s), agenda object identifier(s),topic object identifier(s), and/or the like.

The client devices 101A-101N may be implemented as any computing deviceas defined above. That is, the client devices 101A-101N may also includecircuitry, networked processors, or the like configured to perform someor all of the apparatus-based processes described herein, and mayinclude a suitable network server and/or other type of processing device(e.g., a controller or computing device of the client devices 101-101N).Electronic data received by the shared dynamic collaborativepresentation progression interface server 210 from the client devices101A-101N may be provided in various forms and via various methods. Forexample, the client devices 101A-101N may include desktop computers,laptop computers, smartphones, netbooks, tablet computers, wearables,and/or other networked device, that may be used for any suitable purposein addition to presenting the Shared dynamic collaborative presentationprogression interface to a user and otherwise providing access to thecollaborative presentation progression interface management system 200.The depictions in FIG. 1 of “N” client devices are merely forillustration purposes. According to some embodiments, the client devices101A-101N may be configured to display an interface on a display of theclient device for viewing, editing, and/or otherwise interacting with atleast one Shared dynamic collaborative presentation progressioninterface, which may be provided by the collaborative presentationprogression interface management system 200.

In embodiments where a client device 101A-101N is a mobile device, suchas a smartphone or tablet, the client device 101A-101N may execute an“app” to interact with the collaborative presentation progressioninterface management system 200. Such apps are typically designed toexecute on mobile devices, such as tablets or smartphones. For example,an app may be provided that executes on mobile device operating systemssuch as iOS®, Android®, or Windows®. These platforms typically provideframeworks that allow apps to communicate with one another and withparticular hardware and software components of mobile devices. Themobile operating systems named above each provide frameworks forinteracting with, for example, wired and wireless network interfaces,user contacts, and other applications. Communication with hardware andsoftware modules executing outside of the app is typically provided viaapplication programming interfaces (APIs) provided by the mobile deviceoperating system. Additionally, or alternatively, the client device101A-101N may interact with the collaborative presentation progressioninterface management system 200 via a web browser. As yet anotherexample, the client devices 101A-101N may include various hardware orfirmware designed to interface with the collaborative presentationprogression interface management system 200. Example embodimentscontemplated herein may have various form factors and designs but willnevertheless include at least the components illustrated in FIG. 3 anddescribed in connection therewith.

Example Apparatuses for Implementing Embodiments of the PresentDisclosure

FIG. 2 shows a schematic block diagram of example circuitry, some or allof which may be included in a shared dynamic collaborative presentationprogression interface server 210. In accordance with some exampleembodiments, shared dynamic collaborative presentation progressioninterface server 210 may include various means, such as memory 201,processor 202, input/output circuitry 203, and/or communicationscircuitry 204. Moreover, in some embodiments, shared dynamiccollaborative presentation progression interface circuitry 205 may alsoor instead be included in the shared dynamic collaborative presentationprogression interface server 210. For example, where shared dynamiccollaborative presentation progression interface circuitry 205 isincluded in shared dynamic collaborative presentation progressioninterface server 210, shared dynamic collaborative presentationprogression interface circuitry 205 may be configured to facilitate thefunctionality discussed herein regarding capturing content of one ormore capture types and generating, causing storage of, updating, and/orretrieving shared dynamic collaborative presentation progressioninterface(s). An apparatus, such as shared dynamic collaborativepresentation progression interface server 210, may be configured, usingone or more of the circuitry 201, 202, 203, 204, and 205, to execute theoperations described above with respect to FIG. 1 and below inconnection with FIGS. 4A, 4B, 5-7 and 14-16 .

Although the use of the term “circuitry” as used herein with respect tocomponents 201-205 are described in some cases using functionallanguage, it should be understood that the particular implementationsnecessarily include the use of particular hardware configured to performthe functions associated with the respective circuitry as describedherein. It should also be understood that certain of these components201-205 may include similar or common hardware. For example, two sets ofcircuitry may both leverage use of the same processor, networkinterface, storage medium, or the like to perform their associatedfunctions, such that duplicate hardware is not required for each set ofcircuitry. It will be understood in this regard that some of thecomponents described in connection with the shared dynamic collaborativepresentation progression interface server 210 may be housed within thisdevice, while other components are housed within another of thesedevices, or by yet another device not expressly illustrated in FIG. 1 .

While the term “circuitry” should be understood broadly to includehardware, in some embodiments, the term “circuitry” also includessoftware for configuring the hardware. For example, in some embodiments,“circuitry” may include processing circuitry, storage media, networkinterfaces, input/output devices, and the like. In some embodiments,other elements of the shared dynamic collaborative presentationprogression interface server 210 may provide or supplement thefunctionality of particular circuitry. For example, the processor 202may provide processing functionality, the memory 201 may provide storagefunctionality, the communications circuitry 204 may provide networkinterface functionality, and the like.

In some embodiments, the processor 202 (and/or co-processor or any otherprocessing circuitry assisting or otherwise associated with theprocessor) may be in communication with the memory 201 via a bus forpassing information among components of, for example, shared dynamiccollaborative presentation progression interface server 210. The memory201 is non-transitory and may include, for example, one or more volatileand/or non-volatile memories, or some combination thereof. In otherwords, for example, the memory 201 may be an electronic storage device(e.g., a non-transitory computer readable storage medium). The memory201 may be configured to store information, data, content, applications,instructions, or the like, for enabling an apparatus, e.g., shareddynamic collaborative presentation progression interface server 210, tocarry out various functions in accordance with example embodiments ofthe present disclosure.

Although illustrated in FIG. 2 as a single memory, memory 201 maycomprise a plurality of memory components. The plurality of memorycomponents may be embodied on a single computing device or distributedacross a plurality of computing devices. In various embodiments, memory201 may comprise, for example, a hard disk, random access memory, cachememory, flash memory, a compact disc read only memory (CD-ROM), digitalversatile disc read only memory (DVD-ROM), an optical disc, circuitryconfigured to store information, or some combination thereof. Memory 201may be configured to store information, data, applications,instructions, or the like for enabling shared dynamic collaborativepresentation progression interface server 210 to carry out variousfunctions in accordance with example embodiments discussed herein. Forexample, in at least some embodiments, memory 201 is configured tobuffer data for processing by processor 202. Additionally oralternatively, in at least some embodiments, memory 201 is configured tostore program instructions for execution by processor 202. Memory 201may store information in the form of static and/or dynamic information.This stored information may be stored and/or used by shared dynamiccollaborative presentation progression interface server 210 during thecourse of performing its functionalities.

Processor 202 may be embodied in a number of different ways and may, forexample, include one or more processing devices configured to performindependently. Additionally, or alternatively, processor 202 may includeone or more processors configured in tandem via a bus to enableindependent execution of instructions, pipelining, and/ormultithreading. Processor 202 may, for example, be embodied as variousmeans including one or more microprocessors with accompanying digitalsignal processor(s), one or more processor(s) without an accompanyingdigital signal processor, one or more coprocessors, one or moremulti-core processors, one or more controllers, processing circuitry,one or more computers, various other processing elements includingintegrated circuits such as, for example, an ASIC (application specificintegrated circuit) or FPGA (field programmable gate array), or somecombination thereof. The use of the term “processing circuitry” may beunderstood to include a single core processor, a multi-core processor,multiple processors internal to the apparatus, and/or remote or “cloud”processors. Accordingly, although illustrated in FIG. 2 as a singleprocessor, in some embodiments, processor 202 comprises a plurality ofprocessors. The plurality of processors may be embodied on a singlecomputing device or may be distributed across a plurality of suchdevices collectively configured to function as shared dynamiccollaborative presentation progression interface server 210. Theplurality of processors may be in operative communication with eachother and may be collectively configured to perform one or morefunctionalities of shared dynamic collaborative presentation progressioninterface server 210 as described herein.

In an example embodiment, processor 202 is configured to executeinstructions stored in the memory 201 or otherwise accessible toprocessor 202. Alternatively, or additionally, the processor 202 may beconfigured to execute hard-coded functionality. As such, whetherconfigured by hardware or software methods, or by a combination thereof,the processor 202 may represent an entity (e.g., physically embodied incircuitry) capable of performing operations according to an embodimentof the present disclosure while configured accordingly. Alternatively,as another example, when the processor 202 is embodied as an executor ofsoftware instructions, the instructions may specifically configureprocessor 202 to perform one or more algorithms and/or operationsdescribed herein when the instructions are executed. For example, theseinstructions, when executed by processor 202, may cause shared dynamiccollaborative presentation progression interface server 210 to performone or more of the functionalities of shared dynamic collaborativepresentation progression interface server 210 as described herein.

In some embodiments, shared dynamic collaborative presentationprogression interface server 210 further includes input/output circuitry203 that may, in turn, be in communication with processor 202 to providean audible, visual, mechanical, or other output and/or, in someembodiments, to receive an indication of an input from a user, a clientdevice 101A-101N, audio-video conferencing interface service 105, oranother source. In that sense, input/output circuitry 203 may includemeans for performing analog-to-digital and/or digital-to-analog dataconversions. Input/output circuitry 203 may include support, forexample, for a display, touchscreen, keyboard, button, click wheel,mouse, joystick, an image capturing device (e.g., a camera), motionsensor (e.g., accelerometer and/or gyroscope), microphone, audiorecorder, speaker, biometric scanner, and/or other input/outputmechanisms. Input/output circuitry 203 may comprise a user interface andmay comprise a web user interface, a mobile application, a kiosk, or thelike. The processor 202 and/or user interface circuitry comprising theprocessor 202 may be configured to control one or more functions of adisplay or one or more user interface elements through computer programinstructions (e.g., software and/or firmware) stored on a memoryaccessible to the processor 202 (e.g., memory 201, and/or the like). Insome embodiments, aspects of input/output circuitry 203 may be reducedas compared to embodiments where shared dynamic collaborativepresentation progression interface server 210 may be implemented as anend-user machine or other type of device designed for complex userinteractions. In some embodiments (like other components discussedherein), input/output circuitry 203 may even be eliminated from shareddynamic collaborative presentation progression interface server 210.Input/output circuitry 203 may be in communication with memory 201,communications circuitry 204, and/or any other component(s), such as viaa bus. Although more than one input/output circuitry and/or othercomponent can be included in shared dynamic collaborative presentationprogression interface server 210, only one is shown in FIG. 2 to avoidovercomplicating the disclosure (e.g., like the other componentsdiscussed herein).

Communications circuitry 204, in some embodiments, includes any means,such as a device or circuitry embodied in either hardware, software,firmware or a combination of hardware, software, and/or firmware, thatis configured to receive and/or transmit data from/to a network and/orany other device, circuitry, or module in communication with shareddynamic collaborative presentation progression interface server 210. Inthis regard, communications circuitry 204 may include, for example, anetwork interface for enabling communications with a wired or wirelesscommunication network. For example, in some embodiments, communicationscircuitry 204 is configured to receive and/or transmit any data that maybe stored by memory 201 using any protocol that may be used forcommunications between computing devices. For example, communicationscircuitry 204 may include one or more network interface cards, antennae,transmitters, receivers, buses, switches, routers, modems, andsupporting hardware and/or software, and/or firmware/software, or anyother device suitable for enabling communications via a network.Additionally or alternatively, in some embodiments, communicationscircuitry 204 includes circuitry for interacting with the antenna(s) tocause transmission of signals via the antenna(e) or to handle receipt ofsignals received via the antenna(e). These signals may be transmitted byshared dynamic collaborative presentation progression interface server210 using any of a number of wireless personal area network (PAN)technologies, such as Bluetooth® v1.0 through v3.0, Bluetooth Low Energy(BLE), infrared wireless (e.g., IrDA), ultra-wideband (UWB), inductionwireless transmission, or the like. In addition, it should be understoodthat these signals may be transmitted using Wi-Fi, Near FieldCommunications (NFC), Worldwide Interoperability for Microwave Access(WiMAX) or other proximity-based communications protocols.Communications circuitry 204 may additionally or alternatively be incommunication with the memory 201, input/output circuitry 203 and/or anyother component of shared dynamic collaborative presentation progressioninterface server 210, such as via a bus.

In some embodiments, shared dynamic collaborative presentationprogression interface circuitry 205 may also or instead be included andconfigured to perform the functionality discussed herein related togenerating and updating a shared dynamic collaborative presentationprogression interface(s). In some embodiments, shared dynamiccollaborative presentation progression interface circuitry 205 includeshardware, software, firmware, and/or a combination of such components,configured to support various aspects of such shared dynamiccollaborative presentation progression interface-related functionality,features, and/or services of the shared dynamic collaborativepresentation progression interface server 210 as described herein (e.g.,designed to generate a shared dynamic collaborative presentationprogression interface based upon at least one or more topic objectswithin a topic object sequence set). It should be appreciated that insome embodiments, shared dynamic collaborative presentation progressioninterface circuitry 205 performs one or more of such exemplary actionsin combination with another set of circuitry of the shared dynamiccollaborative presentation progression interface server 210, such as oneor more of memory 201, processor 202, input/output circuitry 203, andcommunications circuitry 204. For example, in some embodiments, shareddynamic collaborative presentation progression interface circuitry 205utilizes processing circuitry, such as the processor 202 and/or thelike, to perform one or more of its corresponding operations. In someinstances, the shared dynamic collaborative presentation progressioninterface circuitry 205 may generates an initial interface that issubsequently modified by captured content data object(s) and/or thelike. In a further example, in some embodiments, some or all of thefunctionality shared dynamic collaborative presentation progressioninterface circuitry 205 may be performed by processor 202. In thisregard, some or all of the example processes and algorithms discussedherein can be performed by at least one processor 202 and/or shareddynamic collaborative presentation progression interface circuitry 205.It should also be appreciated that, in some embodiments, shared dynamiccollaborative presentation progression interface circuitry 205 mayinclude a separate processor, specially configured field programmablegate array (FPGA), or application specific interface circuit (ASIC) toperform its corresponding functions.

Additionally or alternatively, in some embodiments, shared dynamiccollaborative presentation progression interface circuitry 205 utilizesmemory 201 to store collected information. For example, in someimplementations, shared dynamic collaborative presentation progressioninterface circuitry 205 includes hardware, software, firmware, and/or acombination thereof, that interacts with shared dynamic collaborativepresentation progression interface repository 215 and/or memory 201 tosend, retrieve, update, and/or store data values embodied by and/orassociated with shared dynamic collaborative presentation progressioninterface data, user identifier(s), elapsed time identifier(s), targettime identifier(s), agenda object identifier(s), topic objectidentifier(s), and associated data that is configured for associationwith, for example, generating and/or updating a shared dynamiccollaborative presentation progression interface, and to support theoperations of the shared dynamic collaborative presentation progressioninterface circuitry 205 and the remaining circuitry. Additionally oralternatively, in some embodiments, shared dynamic collaborativepresentation progression interface circuitry 205 utilizes input/outputcircuitry 203 to facilitate user output (e.g., causing rendering of oneor more user interface(s) such as a shared dynamic collaborativepresentation progression interface), and/or to receive user input (e.g.,user clicks, user taps, keyboard interactions, user gesture, and/or thelike). Additionally or alternatively still, in some embodiments, theshared dynamic collaborative presentation progression interfacecircuitry 205 utilizes communications circuitry 204 to initiatetransmissions to another computing device, receive transmissions fromanother computing device, communicate signals between the various setsof circuitry as depicted, and/or the like.

Accordingly, non-transitory computer readable storage media can beconfigured to store firmware, one or more application programs, and/orother software, which include instructions and/or othercomputer-readable program code portions that can be executed to controlprocessors of the components of shared dynamic collaborativepresentation progression interface server 210 to implement variousoperations, including the examples shown herein. As such, a series ofcomputer-readable program code portions may be embodied in one or morecomputer program products and can be used, with a device, shared dynamiccollaborative presentation progression interface server 210, database,and/or other programmable apparatus, to produce the machine-implementedprocesses discussed herein. It is also noted that all or some of theinformation discussed herein can be based on data that is received,generated and/or maintained by one or more components of the shareddynamic collaborative presentation progression interface server 210. Insome embodiments, one or more external systems (such as a remote cloudcomputing and/or data storage system) may also be leveraged to provideat least some of the functionality discussed herein.

Referring now to FIG. 3 , the client devices (e.g., client device101A-101N) or the like, may be embodied by one or more computingsystems, such as apparatus 300 shown in FIG. 3 . FIG. 3 is a schematicblock diagram showing example circuitry, some or all of which may beincluded in an example apparatus 300, configured to enable a user toaccess the shared dynamic collaborative presentation progressioninterface management system 200 and/or the audio-video conferencinginterface service 105 in accordance with certain embodiments of thepresent disclosure. For example, in some embodiments, the apparatus 300embodies a client device 101A-101N and is configured to enable a user tointeract with the audio-video conferencing interface service 105 toaccess an active audio-video conference presentation that is configuredfor display to participating client devices and/or the shared dynamiccollaborative presentation progression interface management system 200to capture and/or review selected content.

In accordance with some example embodiments, apparatus 300 may includevarious means, such as memory 301, processor 302, input/output circuitry303, and/or communications circuitry 304. Apparatus 300, such as aclient device 101A-101N, may be configured, using one or more of thecircuitry 301, 302, 303, and 304, to execute the operations describedabove with respect to FIG. 1 and below in connection with FIGS. 4-7 .

In some embodiments, apparatus 300 communicates with shared dynamiccollaborative presentation progression interface management system 200(for example, embodied by the shared dynamic collaborative presentationprogression interface server 210 as depicted and described with respectto FIG. 2 ). It should be appreciated that, in some embodiments, ashared dynamic collaborative presentation progression interfacemanagement system 200 communicates with any number of apparatus(es) 300.It should be appreciated that the components 301-304 may be embodiedsimilar to that of the similarly named components described with respectto FIG. 2 . For purposes of brevity and length of disclosure, duplicatedescription of such functionality is omitted. Nevertheless, these deviceelements, operating together, provide the respective apparatuses withthe functionality necessary to facilitate the communication of data(e.g., shared dynamic collaborative presentation progression interfacedata, user identifier(s), elapsed time identifier(s), target timeidentifier(s), agenda object identifier(s), topic object identifier(s),and/or the like) for generating a shared dynamic collaborativepresentation progression interface. That is, the apparatus 300, in someembodiments, is configured, using one or more sets of circuitry 301,302, 303, and/or 304, to execute the operations described herein.

As described above and as will be appreciated based on this disclosure,embodiments of the present disclosure may be configured as systems,methods, apparatuses, computing devices, personal computers, servers,mobile devices, backend network devices, and the like. Accordingly,embodiments may comprise various means including entirely of hardware orany combination of software and hardware. Furthermore, embodiments maytake the form of a computer program product on at least onenon-transitory computer-readable storage medium having computer-readableprogram instructions embodied in the computer-readable storage medium(e.g., computer software stored on a hardware device). Any suitablecomputer-readable storage medium may be utilized includingnon-transitory hard disks, CD-ROMs, flash memory, optical storagedevices, or magnetic storage devices.

As will be appreciated, any such computer program instructions and/orother type of code may be loaded onto a computer, processor or otherprogrammable apparatus's circuitry to produce a machine, such that thecomputer, processor, or other programmable circuitry that execute thecode on the machine creates the means for implementing variousfunctions, including those described herein in connection with thecomponents of shared dynamic collaborative presentation progressioninterface server 210 and client devices 101A-101N.

The computing systems described herein can include clients and servers.A client and server are generally remote from each other and typicallyinteract through a communication network. The relationship of client andserver arises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someembodiments, a server transmits information/data (e.g., an HTML page) toa client device (e.g., for purposes of displaying information/data toand receiving user input from a user interacting with a client device oran admin user interacting with an admin device). Information/datagenerated at the client device (e.g., as a result of the userinteraction with an admin device) can be received from the client device(e.g., client device or admin device) at the server.

Example Operations for Generating, Updating, and/or Otherwise Managing aShared Dynamic Collaborative Presentation Progression Interface

The method, apparatus (e.g., shared dynamic collaborative presentationprogression interface server 210), and computer program product of anexample embodiment will now be described in conjunction with theoperations illustrated in FIGS. 4A-7 .

With reference to FIG. 4A, a flowchart is provided broadly illustratinga series of operations or process blocks for shared dynamiccollaborative presentation progression interface generation inassociation with an audio-video conferencing interface service, inaccordance with some example embodiments of the present disclosure. Theoperations illustrated in FIG. 4A may, for example, be performed by,with the assistance of, and/or under the control of one or moreapparatuses, such as shared dynamic collaborative presentationprogression interface server 210, as described above. In this regard,performance of the operations may invoke one or more of memory 201,processor 202, input/output circuitry 203, communications circuitry 204,and/or collaborative contextual summary interface circuitry 205. Certainoperations may be considered optional, as indicated by the dashed lines.

As shown in operation 405, the apparatus (e.g., shared dynamiccollaborative presentation progression interface server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, and/or the like, for monitoring an active audio-videoconference presentation that is configured for rendering to respectivedisplays of a plurality of participating client devices by anaudio-video conferencing interface service. By way of example, prior toor during an active audio-video conference presentation, a user providesthe shared dynamic collaborative presentation progression interfaceserver 210 with access to the active audio-video conferencepresentation. For example, in some embodiments, the user provides theshared dynamic collaborative presentation progression interface serverwith access by simply providing login credentials and data of theaudio-video conferencing interface services to the shared dynamiccollaborative presentation progression interface server 210. In someembodiments, the user may provide the shared dynamic collaborativepresentation progression interface server with access by grantinglimited access to a protocol such as an open-standard authorizationprotocol like OAuth (e.g., OAuth 1.0, OAuth 2.0, or any such OAuthversion hereinafter generated or created). In some embodiments, a usermay provide credentials, consent, and/or privileges to the shareddynamic collaborative presentation progression interface server to allowthe shared dynamic collaborative presentation progression interfaceserver to share a token to the open-standard authorization protocol, forthe open-standard authorization protocol to access the shared dynamiccollaborative presentation progression interface server and/or shareddynamic collaborative presentation progression interface for a specificagenda object or meeting. In some embodiments, an admin device mayprovide credentials, privileges, and/or consent to the shared dynamiccollaborative presentation progression interface server to share a tokento the open-standard authorization protocol, for the open-standardauthorization protocol to access the shared dynamic collaborativepresentation progression interface server and/or shared dynamiccollaborative presentation progression interface for all agendas and/ormeetings within a specified time period, for specified participatingusers, and/or for access to all meetings within a specific organization.

In some embodiments, the active audio-video conference presentation is alive streaming presentation displayed in real time by the audio-videoconferencing interface service to each of the participating clientdevices. By way of non-limiting example, Alice, Beth and Cheri are usersaccessing and participating in a live virtual meeting as it is displayedin real time. Client devices 101A-101N associated with the useridentifiers corresponding to Alice, Bethany and Cheri are known asparticipating client devices. In still other embodiments, the activeaudio-video conference presentation is a stored playback presentationthat is configured to be displayed to participating client devicesand/or non-participating client devices. By way of non-limiting example,after completion of the live streaming presentation, Alice can use herparticipating client device to access a stored playback presentation ofthe active audio-video conference presentation. In a furthernon-limiting example, Debbie, who did not participate in the livevirtual meeting, can use her non-participating client device to accessthe stored playback presentation and to access the specific time periodsassociated with each topic object of the topic object sequence set(e.g., by a selectable link), such that Debbie may access only thespecific time period of the audio-video presentation associated with theselected topic object.

As shown by operation 410, the apparatus (e.g., collaborative contextualsummary interface server 210) includes means, such as processor 202,input/output circuitry 203, communications circuitry 204, collaborativecontextual summary interface circuitry 205 and/or the like, forgenerating a shared dynamic collaborative presentation progressioninterface. In some embodiments, the shared dynamic collaborativepresentation progression interface is generated by a shared dynamiccollaborative presentation progression interface server 210 andtransmitted to one or more client devices 101A-101N. In someembodiments, the shared dynamic collaborative presentation progressioninterface is associated with a topic object sequence set.

In some embodiments, the shared dynamic collaborative presentationprogression interface is configured for rendering to the respectivedisplays of the plurality of participating client devices in associationwith the active audio-video conference presentation. Each client device101A-101N may comprise a GUI configured by the shared dynamiccollaborative presentation progression interface, wherein each instanceof the shared dynamic collaborative presentation progression interfaceon each client device 101A-101N may comprise the same content data ofthe shared dynamic collaborative presentation progression interface inone or more different interface embodiments. By way of example, theaudio-video conference presentation may be used to configure the GUI ofthe participating client devices to each of the one or moreparticipating client devices. For example, an audio-video conferencinginterface server 105 may be in communication with the collaborativepresentation progression interface management system 200, and by way ofthe collaborative presentation progression interface management system200 in communication with one or more client devices 101A-101B vianetwork, the audio-video conference presentation generated using theaudio-video conference interface server 105 may be transmitted as ashared dynamic collaborative presentation progression interface to theone or more client devices.

By way of non-limiting example, the shared dynamic collaborativepresentation progression interface of the participating client deviceassociated with Alice may comprise content (e.g., an audio-videoconference presentation) in a specified format (e.g., the icons of theshared dynamic collaborative presentation progression interface maycomprise one set of sizes; text of the shared dynamic collaborativepresentation progression interface may comprise different fonts, sizes,italicizing, bolding, highlighting, and other such design elements ofthe participating client device and associated interface). Further, byway of non-limiting example, the shared dynamic collaborativepresentation progression interface of the participating client deviceassociated with Beth may comprise the same interface element as Alice,but in one or more different formats. Such specified formats in theshared dynamic collaborative presentation progression interface may becontrolled locally on the participating client devices by way of one ormore user-selected settings and/or device-specific settings. Suchexample embodiments of the shared dynamic collaborative presentationprogression interface configured on a client device may be shown inFIGS. 13, 14, 15, and 16 , as interfaces 1300, 1400, 1500, and 1600,respectively.

As shown by operation 415, the apparatus (e.g., collaborative contextualsummary interface server 210) includes means, such as processor 202,input/output circuitry 203, communications circuitry 204, collaborativecontextual summary interface circuitry 205 and/or the like, fortransmitting the shared dynamic collaboration presentation progressioninterface to the plurality of participating client devices. By way ofexample, and as discussed hereinabove, the shared dynamic collaborationpresentation progression interface may be transmitted to one or moreclient devices 110A-110N from the collaborative presentation progressioninterface management system 200 via network 102.

As shown by operation 420, the apparatus (e.g., collaborative contextualsummary interface server 210) includes means, such as processor 202,input/output circuitry 203, communications circuitry 204, collaborativecontextual summary interface circuitry 205 and/or the like, forreceiving an initiate topic object sequence set event from at least oneparticipating client device of the plurality of participating clientdevices. By way of non-limiting example, in association with an activeaudio-video conference presentation, a user (e.g., Alice) may interactwith a client device 101A-101N that is in network communication with thecollaborative presentation progression interface management system 200to initiate, or start, an audio-video conference presentation. Such anindication (e.g., initiate topic object sequence set event) may comprisethe user selecting an element (e.g., a “button” configured to beelectronically selected on a client device) on a configured GUI of theclient device to start the audio-video conference presentation, whereinthe initiate topic object sequence set event may be transmitted from theclient device 101A-101N to the shared dynamic collaborative presentationprogression interface server 210 and received as an initiate topicobject sequence set event. The initiate topic object sequence set eventreceived by the shared dynamic collaborative presentation progressioninterface server 210 and transmitted from the client device 101A-101Nincludes, in some embodiments, various metadata relating to the initiatetopic object sequence set event request by the first user via the clientdevice 101A-101N. By way of non-limiting example, the initiate topicobject sequence set event may be shown as a configured GUI comprising anelectronically selectable “button” such as the ones shown as 825 in FIG.8 (a button which may read, “Get Started”), 1005 in FIG. 10 (a buttonwhich may read, “Get Started”), and/or 1310 in FIG. 13 (a button whichmay read, “Start Meeting”).

As shown by operation 425, the apparatus (e.g., collaborative contextualsummary interface server 210) includes means, such as processor 202,input/output circuitry 203, communications circuitry 204, collaborativecontextual summary interface circuitry 205 and/or the like, foridentifying a first topic object of the topic object sequence set as anactive topic object. In some embodiments, the identification of a firsttopic object of the topic object sequence set as an active topic objectmay occur in response to the shared dynamic collaborative presentationprogression interface server 210 receiving the initiate topic objectsequence set event. In some embodiments, one or more users of theparticipating client devices may interact with a client device 101A-101Nthat is in network communication with the shared dynamic collaborativepresentation progression interface server 210 to generate a topic objectsequence set comprising one or more topic objects. By way ofnon-limiting example, one or more users of the participating clientdevices may interact with the shared dynamic collaborative presentationprogression interface server 210 via a network to generate a topicobject sequence set comprising one or more topic objects, such as anagenda of the audio-video conference presentation. In some embodiments,the one or more users of the participating client devices in associationwith the shared dynamic collaborative presentation progression interfaceserver 210 may select and/or otherwise identify a specific order of thetopic objects in the topic object sequence set (e.g., a specified orderof discussion for each of the topic objects associated with the topicobject sequence set). In some embodiments, such selection and/oridentification occurs prior to the audio-video conference presentation.By way of non-limiting example, the identification of a first topicobject of the topic object sequence set as an active topic object maycomprise selecting a topic object of the topic object sequence set whichwas previously identified as a first topic object for the audio-videoconference presentation (e.g., a first topic object for discussion inthe audio-video conference presentation) prior to the start of theaudio-video conference presentation by one or more users collaboratingto generate such topic object sequence set (e.g., agenda). Additionallyor alternatively, in still further embodiments, such selection and/oridentification occurs during the audio-video conference presentation. Byway of non-limiting example, the identification of a first topic objectof the topic object sequence set as an active topic object may compriseselecting a topic object of the topic object sequence set as a firsttopic object for the audio-video conference presentation (e.g., a firsttopic object for discussion in the audio-video conference presentation)in real-time during the audio-video conference presentation by one ormore users participating in the audio-video conference presentation. Insome embodiments, a timer is activated by the apparatus (e.g.,collaborative contextual summary interface server 210) in associationwith identifying the first topic object as the active topic object atoperation 425.

In some embodiments, once a topic object sequence set has been selectedby a user by the transmission of the initiate topic object sequence setevent to the shared dynamic collaborative presentation progressioninterface server 210, and once the topic object sequence set has begun(e.g., once the audio-video conference presentation has started), one ormore participating users may select a different topic object sequenceset (e.g., transmit a different initiate topic object sequence set eventto the shared dynamic collaborative presentation progression interfaceserver 210) in real-time and during the current topic object sequenceset to restart the first-selected topic object sequence set to adifferent and/or second topic object sequence set.

In some embodiments, the active topic object of the topic objectsequence set may comprise a visual emphasis element indicating theactive topic object as the current topic of the topic object sequenceset in the audio-video conference presentation. By way of non-limitingexample, the active topic object may be shown as a configured GUIcomprising an element of shared dynamic collaborative presentationprogression interface as element 1115 in FIG. 11 (the topic object whichreads, “The First Ivy User” which is currently being discussed), 1405 ofFIG. 14 (topic object which reads, “Intros” which is currently beingdiscussed), and/or 1510 of FIG. 15 (topic object which reads, “Person 2Turn” which is currently being discussed).

Additionally or alternatively, in some embodiments, the visualrepresentation of the first topic object and other topic objects of thetopic object sequence set may comprise a selectable link. In someembodiments, a user may select the link associated with the topicobjects and, in response to the selected link, the participating clientdevice may transmit a request comprising a topic object identifier tothe shared dynamic collaborative presentation progression interfaceserver 210 to access a resource object associated with the selectedtopic object and its topic object identifier. In some embodiments, theshared dynamic collaborative presentation progression interface server210 may query the shared dynamic collaborative presentation progressioninterface repository 215 to access the resource object associated withthe topic object identifier and may transmit the resource object of thetopic object identifier (e.g., by way of the shared dynamiccollaborative presentation progression interface server 215) back to theparticipating client device for rendering on a configured GUI of theparticipating client device. By way of non-limiting example, such aresource object may comprise presentation slides, reading materials,webpages, etc. associated with the audio-video conference presentationfor the specified topic object of the topic object identifier.

Additionally or alternatively, in some embodiments wherein a secondtopic object is associated with a second participating user identifier,the apparatus (e.g., collaborative contextual summary interface server210) includes means, such as processor 202, input/output circuitry 203,communications circuitry 204, collaborative contextual summary interfacecircuitry 205 and/or the like, for, in response and/or in addition toidentifying the first topic object of the topic object sequence set asthe active topic object, transmitting a display upcoming presenternotification event to the participating client device associated withthe second participating user identifier, such display upcomingpresenter notification event comprising instructions for configuring theGUI to indicate to the specific user of the participating client device(e.g., second participating user) that the topic object associated withthe user is upcoming in the topic object sequence set (e.g., to getready to present soon). In some embodiments, a participating user deviceassociated with the active topic object (e.g., the participating user ofthe active topic object) may receive a notification event similar to theupcoming presentation notification event, but wherein the notificationevent of the participating user of the active topic object may benotified that a target time of the active topic object is almostsatisfied. By way of non-limiting example, a participating client devicemay receive a notification event comprising instructions for configuringthe GUI to indicate to the participating user of the active topic object(e.g., a first participating user) that the topic object associated withthe participating user has a target time that has almost been met,satisfied, or exceeded. In some embodiments, the participating clientdevice may receive the notification event and configure the GUI of theparticipating user device at user-specified time intervals leading up tothe end of the target time (e.g., 2 mins before target time is met, 1minute before target time is met, 30 seconds before target time is met,and other such predefined time periods). In some embodiments, theparticipating client device may receive the notification event andconfigure the GUI of the participating user device atprogrammatically-specified time intervals leading up to the target time(e.g., 2 mins before target time is met, 1 minute before target time ismet, 30 seconds before target time is met, and other such predefinedtime periods). By way of example, and in some embodiments, theparticipating client device may receive the notification event andconfigure the GUI of the participating user device associated with theactive topic object at the same time the upcoming presenter notificationevent configures and/or is presented on the participating user device ofthe sequential (e.g., next) topic object.

In some embodiments, the target time associated with each of the topicobjects of a topic object sequences set and/or a facilitation topicobject may be programmatically selected and/or manually generated by oneor more participating users of the shared dynamic collaborativepresentation progression interface. In some embodiments, the shareddynamic collaborative presentation progression interface server 210 mayprogrammatically generate the target time for each of the topic objects(e.g., in a topic object sequence set and/or facilitation topic object)based upon one or more identifiers, such as user identifier(s), agendaobject identifier(s), topic object identifier(s), and/or the like. Byway of non-limiting example, the shared dynamic collaborativepresentation progression interface may programmatically select and/orgenerate a target time for each of the topic objects by analyzing to theamount (e.g., number) of participating users (e.g., by referring to theparticipating user identifiers) and/or the amount of topic objectswithin the topic object sequence set to determine how much time may beused for each topic object associated with each of the participatinguser identifiers (e.g., for an audio-video conference presentationscheduled for one hour and with 6 topic objects comprising twoparticipating user identifiers per topic object, the shared dynamiccollaborative presentation progression interface server 210 may generatea target time for each topic object as 10 minutes. By way ofnon-limiting example, and in further reference to the example describedhereinabove, if 3 topic objects comprising 2 participating user devicesfor the identified for the first two topic objects and 4 participatinguser devices are identified for the last topic object, the shareddynamic collaborative presentation progression interface server 210 mayindicate a target time for the first two topics as 15 minutes and 30minutes for the last topic objects such that the target times aredetermined based on a ratio of topic objects to participating userdevices.

As shown by operation 430, the apparatus (e.g., collaborative contextualsummary interface server 210) includes means, such as processor 202,input/output circuitry 203, communications circuitry 204, collaborativecontextual summary interface circuitry 205 and/or the like, for updatingthe shared dynamic collaborative presentation progression interface tocause rendering of at least an active visual emphasis element inassociation with a visual representation the first topic object. In someembodiments, the shared dynamic collaborative presentation progressioninterface rendered on each of the client devices 101A-101N inassociation with the audio-video conference presentation may comprise anupdate of the shared dynamic collaborative presentation progressioninterface by rendering the first topic object of the topic objectsequence set as an active topic object on each of the one or more clientdevices (e.g., by configured the GUI of each of the one or more clientdevices to indicate the active topic object). By way of non-limitingexample, the shared dynamic collaborative presentation progressioninterface may highlight or indicate that the first topic object of theone or more topic objects within a topic object sequence set is theactive topic object such as that shown as element 1115 in FIG. 11 (thetopic object of “The First Ivy User,” wherein the GUI is configured toshow the topic object the only topic covered by stating “0 topiccovered”), 1405 of FIG. 14 (topic object of “Intros,” wherein the GUI isconfigured to show the “Intros” as the only topic object to be discussedand/or currently being discussed), and/or 1510 of FIG. 15 (topic object“Person 2 Turn,” wherein the GUI is configured to show “Person 2 Turn”in a different element indicating a special status which may comprise abox around the topic object). Additionally or alternatively, in someembodiments, the visual representation of the first topic object (e.g.,active topic object) includes a visual indication of a timespent/associated with the topic object (e.g., elapsed time object) beingthe active topic object. In still further embodiments, the elapsed timeobject corresponds to a timer activated by the apparatus (e.g.,collaborative contextual summary interface server 210) in associationwith identifying the first topic object as the active topic object atoperation 425. Additionally or alternatively, in some embodiments,wherein a first participating user identifier is associated with thefirst topic object, the visual representation of the first topic object(e.g., active topic object) includes display of a visual representationof the first participating user identifier in association with thevisual representation of the first topic object. In some embodiments,the active topic object may be indicated by an element configured on theGUI of one or more participating user devices by the shared dynamiccollaborative presentation progression interface to show only the activetopic object within a topic object sequence set. By way of non-limitingexample, the configured GUI showing only the active topic object topicobject sequence set may be shown by element 1420 of FIG. 14 , which mayindicate the active topic object (e.g., an introduction of Luis) withinan element comprising a pop-up, square, colored box/square, itemizedlist comprising the active topic object, and/or other such elementsindicating a single topic object as an active topic object.

In some embodiments, the shared dynamic collaborative presentationprogression interface comprises display of only the active topic object.Alternatively, the shared dynamic collaborative presentation progressioninterface comprises a visual representation of one or more other topicobjects, such as the topic object sequence set

FIG. 4B is a signal diagram of an example data flow represented by theoperations depicted in FIG. 4A. That is, FIG. 4B illustrates an examplesignal diagram illustrating data flow interactions between a shareddynamic collaborative presentation progression interface server, aclient device, and a repository, when generating a shared dynamiccollaborative presentation progression interface in accordance with oneembodiment. FIG. 4B is described as being performed by a shared dynamiccollaborative presentation progression interface server 210, a shareddynamic collaborative presentation progression interface repository 215,and a client device 101A. These may be similar to those previouslydiscussed with regards to FIG. 1 .

With reference to FIG. 5 , a flowchart is provided broadly illustratinga series of operations or process blocks for generating and transmittinga transition topic object sequence instructions set for updating theshared dynamic collaborative presentation progression interface inassociation with an audio-video conferencing interface service, inaccordance with some example embodiments of the present disclosure. Theoperations illustrated in FIG. 5 may, for example, be performed by, withthe assistance of, and/or under the control of one or more apparatuses,such as shared dynamic collaborative presentation progression interfaceserver 210, as described above. In this regard, performance of theoperations may invoke one or more of memory 201, processor 202,input/output circuitry 203, communications circuitry 204, and/orcollaborative contextual summary interface circuitry 205. Certainoperations may be considered optional, as indicated by the dashed lines.

As shown in operation 505, the apparatus (e.g., shared dynamiccollaborative presentation progression interface server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, and/or the like, for receiving a topic object progressionevent from at least one participating client device of the plurality ofparticipating client devices. In some embodiments, the topic objectprogression event may be received by the shared dynamic collaborativepresentation progression interface server 210 from one or more clientdevices 101A-101N, wherein one or more requests and or indications byuser(s) of participating client device(s) may comprise electronicindications transmitted to the shared dynamic collaborative presentationprogression interface server 210 to proceed to the next topic object ofthe topic object sequence set. By way of non-limiting example, theshared dynamic collaborative presentation progression interface used toconfigure the GUI of a client device 101A-101N may compriseelectronically selectable elements (e.g., topic object progressioninterface component) for a user of the client device 101A-101N totransition to next topic via a topic object progression event such aselement 1120 of FIG. 11 (e.g., a button which may read, “Next Topic”).

In some embodiments, one or more participating users (e.g., by one ormore participating client devices) may transmit one or more requests tothe shared dynamic collaborative presentation progression interfaceserver 210 to add one or more topics (e.g., topic objects) to the topicobject sequence set during an audio-video conference presentation. Byway of non-limiting example, a participating user may select aninterface element to transmit to the shared dynamic collaborativepresentation progression interface a request to add a new topic to atopic object sequence set while the topic object sequence set is inprogression during an audio-video conference presentation. Additionallyor alternatively, in some embodiments, a participating user of theshared dynamic collaborative presentation progression interface may editone or more topic objects (e.g., an active topic object and/or one ormore topic objects not yet identified as an active topic object or acompleted topic object) in the topic object sequence set when the topicobject sequence set is in progression (e.g., during an audio-videoconference presentation).

In some embodiments, the shared dynamic collaborative presentationprogression interface server 210 may automatically continue to the nexttopic object of the topic object sequence set once some predeterminedrule has been satisfied, such as a predetermined time period for thecurrent topic object has been satisfied. In some embodiments, the shareddynamic collaborative presentation progression interface server 210 maycontinue to the next topic object of the topic object sequence set basedupon a request received from the one or more participating clientdevices indicating a request by one or more participating users toprovide one or more new rules to control the topic object sequence setand subsequent topic objects. By way of non-limiting example, aparticipating user may request, by a participating client device, maytransmit at least one request and/or vote to give a topic object (1)more time in the topic object sequence set, (2) to continue to the nexttopic object, and/or (3) an impartial request to indicate that theparticipating user would allow more time (e.g., option (1)) or willcontinue to the next topic object (e.g., option (2)). In someembodiments, the requests by the participating users may be used by theshared dynamic collaborative presentation progression interface server210 to determine whether to continue to the next topic object of thetopic object sequence set by tallying and/or counting the requests bythe participating users (e.g., if more users select to have more time,then the current active topic object may continue; if more users selectto continue to the next topic object, then the shared dynamiccollaborative presentation progression interface may indicate the nexttopic object is the active topic object; if more users select option (3)and is impartial, then the shared dynamic collaborative presentationprogression interface may be pre-programmed to stay on the current topicobject or the shared dynamic collaborative presentation progressioninterface may be pre-programmed to continue to the next topic object).In some embodiments, such a predetermined time period for the topicobjects of the topic object sequence set may be determined by one ormore users of the participating client devices, wherein the one or moreusers may select (e.g., from a menu of predetermined time period of theshared dynamic collaborative presentation progression interface) or maygenerate (e.g., by inputting into the shared dynamic collaborativepresentation progression interface a specified time period).

In some embodiments, such a predetermined time period for each topicobject may be used by the shared dynamic collaborative presentationprogression interface to indicate a time spent (e.g., elapsed timeobject) on the one or more topic objects of the topic object sequenceset in order to indicate a total time elapsed on the topic objectsequence set. In some embodiments, the total time elapsed on the topicobject sequence set may be updated after each topic object has beencompleted (e.g., completed topic object), such that the total timeelapsed is only updated after a topic object previously identified as anactive topic object is de-identified as the topic object and identifiedas a completed topic object (i.e., the topic object comprises acompleted topic object identifier). By way of non-limiting example, theshared dynamic collaborative presentation progression interface used toconfigure a GUI of one or more client devices 101A-101N may comprise anelement indicating a total time elapsed such as 820 of FIG. 8, 1025 ofFIG. 10, 1105 of FIGS. 11 , and/or 1125 of FIG. 11 . By way ofnon-limiting example, the shared dynamic collaborative presentationprogression interface used to configure the GUI of one or more clientdevices 101A-101N may comprise an elapsed time for each topic object ofthe topic object sequence set such as elements 1110 of FIG. 11(indicating “0:02” or two seconds have elapsed in the current and/oractive topic object), 1405 of FIG. 14 and 1505 of FIG. 15 (bothindicating “0:12” or twelve seconds have elapsed in the current and/oractive topic object), 1610 of FIG. 16 (indicating “4:40” or four minutesand forty seconds have elapsed of the first topic object), 1620(indicating “13:08” or thirteen minutes and eight seconds have elapsedof the second topic object), 1635 of FIG. 16 (indicating “15:32” orfifteen minutes and thirty-two seconds have elapsed of the third topicobject), 1650 of FIG. 16 (indicating “11:21” or eleven minutes andtwenty-one seconds have elapsed of the fourth topic object), 1665 ofFIG. 16 (indicating “8:40” or eight minutes forty seconds have elapsedof the fifth topic object), or 1675 of FIG. 16 (indicating “2:45” or twominutes and forty-five seconds have elapsed of the sixth topic object).

In some embodiments, each topic object of the topic object sequence setmay comprise, be associated with, and/or be assigned a target time foreach of the topic objects to be discussed. For example, each of thetopic objects may comprise target time for the topic object to beidentified as an active topic object. Additionally or alternatively, insome embodiments, the shared dynamic collaborative presentationprogression interface server 210 causes display of a visualrepresentation of the respective target time in association with eachtopic object that is not associated with a completed topic objectidentifier or an active topic object identifier.

Additionally or alternatively, in some embodiments, visual emphasiselements are employed as a contextually relevant coloring scheme tovisually indicate a comparison of the elapsed time to the respectivetarget time of such topic object. By way of non-limiting example, as atopic object is identified as active (e.g., discussed), an elapsed timermay run and as the elapsed timer on the shared dynamic collaborativepresentation progression interface runs, a visual emphasis element maybe assigned and/or added to an elapsed time object to indicate if theelapsed time object exceeds the target time. For example, if the elapsedtime exceeds the target time, a visual emphasis element may indicatethat the time has run for that specific topic object and the associatedpresenter must finish, such as a color highlight of the elapsed timeobject like the color red. For example, and if the elapsed time objectdoes not exceed or meets the target time, a visual emphasis element mayindicate that the target time has not been met, such as by colorhighlighting the elapsed time object the color green. Additionally oralternatively, with respect to completed topic objects, in someembodiments, the shared dynamic collaborative presentation progressioninterface server 210 determines an elapsed time for each completed topicobject and causes display of a visual representation of the respectiveelapsed time in association with each completed topic object. The shareddynamic collaborative presentation progression interface server 210further determines a visual emphasis element for each completed topicobject based at least in part on the respective target time, whereineach visual emphasis element employs a contextually relevant coloringscheme to visually indicate a comparison of the elapsed time for thecompleted topic object to the respective target time of each completedtopic object and applies the determined visual emphasis elements to thevisual representations of the respective elapsed time in associationwith each completed topic object. In some embodiments, the visualemphasis element of an elapsed time object may change and/or bedetermined based upon a target time object and the associated differencebetween the target time object and the elapsed time object. By way ofnon-limiting example, as an elapsed time object runs and/or progressesit may comprise a visual emphasis element of a white color (e.g., theelapsed time object—numbers—may comprise the color white); as an elapsedtime object runs and/or progresses closer to the target time object(e.g., is within 5 minutes, 4 minutes, 3 minutes, 2 minutes, 1 minute,or less than a minute to satisfying the target time object), the elapsedtime object may be indicated with a visual emphasis element to warn oneor more participating users (e.g., the elapsed time object—itsnumbers—may comprise the color yellow or orange); and as the elapsedtime object satisfies and/or runs longer than the target time object,the elapsed time object may be indicated with a visual emphasis elementto warn participating users that the target time has been satisfied(e.g., the elapsed time object—its numbers—may comprise the color red).In some embodiments, the determination of the visual emphasis elementand the point at which the visual emphasis element may change (e.g.,from white to yellow and from yellow/orange to red) may be manuallyprogrammed by a participating user and/or may be programmaticallyselected by the shared dynamic collaborative presentation progressioninterface server 210.

As shown in operation 510, the apparatus (e.g., shared dynamiccollaborative presentation progression interface server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, and/or the like, for de-identifying the first topicobject as the active topic object. In some embodiments, thede-identification of topic object as an active topic object may comprisethe dissociation of an active topic object identifier from the firsttopic object, the association of the first topic object with a completedtopic object identifier (e.g., the identification of the de-identifiedtopic object as a completed topic object), and, in some furtherembodiments, storage of an elapsed time object (e.g., such as describedwith respect to operation 425) that coincides with the receipt of thetopic object progression event in association with the completed firsttopic object. By way of non-limiting example, the de-identification ofthe topic object may comprise the shared dynamic collaborativepresentation progression interface server 210 moving the active visualemphasis element to a new active topic object (e.g., removing an activevisual emphasis element from the de-identified active topic object andapplying an active visual emphasis element to a different topic object,e.g., as discussed in further detail below with respect to operations515 and 525).

In some embodiments, once a topic object has been identified as acompleted topic object, an annotation summary of the completed topicobject may be displayed on the one or more client devices, which maycomprise the participating client devices, wherein the annotationsummary may comprise the title of each topic object, a participatinguser identifier to show the responsible participating user (e.g., suchas an icon, username, full name, picture graphic, and other suchidentifying objects), notes for each topic object that may have beenuploaded by one or more users of the participating client devices,elapsed time objects, and/or visual emphasis elements. In someembodiments, the annotation summary may comprise a summary listing ofcontent captured in association with the first topic object during theperiod of time the first topic object was identified as the active topicobject, such as content to describe the content of the topic objectdiscussed and/or presented in the audio-video conference presentationduring the time at which the topic object was identified as an activetopic object. By way of non-limiting example, the summary listing ofcontent may comprise summaries of the content discussed at the time thetopic object was identified as active (e.g., during the period of timethe topic object was identified as the active topic object), such astext input by one or more users of the participating client devices todisclose each user's interpretation of the active topic object.

As shown in operation 515, the apparatus (e.g., shared dynamiccollaborative presentation progression interface server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, and/or the like, for identifying a second topic object asthe active topic object in the topic object sequence set as the activetopic object. In some embodiments, the identification of a second topicobject as an active topic object may comprise the identification of thede-identified first topic object, of operation 510, as a completed topicobject. In some embodiments, the identification of an active topicobject to a subsequent topic object of the topic object sequence set maycomprise identifying any topic object within the topic object sequenceset as active. For example, in some embodiments, identifying a topicobject (e.g., the second topic object in the topic object sequence set)as the active topic object comprises associating the selected topicobject (e.g., the second topic object) with an active topic objectidentifier.

In some embodiments, the active topic object may be indicated by anactive visual emphasis element. By way of non-limiting example, such anactive visual emphasis element may be shown as element 1510 of FIG. 15which may indicate an active topic object using one or more visualemphasis element types (e.g., by a box like that seen at 1510; by ahighlight; by a shading around the active topic object; by a formattingindication such as italicize, bolding, underling, larger font size; andother such indicators of an active topic object).

As shown in operation 520, the apparatus (e.g., shared dynamiccollaborative presentation progression interface server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, and/or the like, for generating a transition topic objectsequence instructions set based on the topic object progression event.In some embodiments, the shared dynamic collaborative presentationprogression interface server 210 may transmit one or more instructionsto one or more client devices 101A-101N, including the one or moreparticipating client devices, to configure the GUI of each client deviceto update the interfaces of the client devices to indicate a next topicobject. Additionally or alternatively, in some embodiments, wherein asecond participating user identifier is associated with the second topicobject, the transition topic object sequence instructions set includeone or more instructions fore displaying a visual representation of thesecond topic object (e.g., active topic object) with a visualrepresentation of the second participating user identifier inassociation with the visual representation of the second topic object

As shown in operation 525, the apparatus (e.g., shared dynamiccollaborative presentation progression interface server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, and/or the like, for outputting the transition topicobject sequence instruction set to the plurality of participating clientdevices for updating the shared dynamic collaborative presentationprogression interface. In some embodiments, the indication of the nexttopic object by way of the transition topic object sequence instructionsset may comprise indicating the next topic object using a visualemphasis element. By way of non-limiting example, a visual emphasiselement to indicate the next topic object may comprise a generalstatement of the amount of topic objects left to be discussed such asthe element 1130 in FIG. 11 (indicating “6 more topics” in the topicobject sequence set). By way of non-limiting example, a visual emphasiselement to indicate the next topic object may also comprise a list ofthe upcoming topic objects for discussion and/or a list of presentersand/or users associated with the participating client devices who areassigned to each topic object of the upcoming topic objects, such asthat shown in elements 1515, 1520, and 1525 of FIG. 15 (indicating theupcoming or “Up Next” presenters as “Her,” “You,” and “Him”). Each ofthese visual emphasis elements used to indicate the next topic object orplurality of next topic objects (which may also comprise one or morepresenters assigned to each topic object) may be used by the shareddynamic collaborative presentation progression interface server 210 toconfigure the GUI of the one or more client devices 101A-101N, furthercomprising the one or more participating client devices.

In some embodiments, updating the shared dynamic collaborativepresentation progression interface comprises causing stopping of therendering of the active visual emphasis element in association with thevisual representation of the first topic object and causing rendering ofthe active visual emphasis element in association with the visualrepresentation of the second topic object. By way of non-limitingexample, such an active visual emphasis element may be shown as element1510 of FIG. 15 . Additionally or alternatively, in association withcausing stopping of the rendering of the active visual emphasis elementwith respect to the visual representation of the first topic object, insome embodiments, the apparatus (shared dynamic collaborativepresentation progression interface server 210) causes display of acompletion indicator in association with the visual representation ofthe first topic object. By way of further non-limiting example, theupdating of shared dynamic collaborative presentation progressioninterface comprising the stopping of the rendering of the active visualemphasis element in association with the first topic object may furthercomprise the transmission of an updated shared dynamic collaborativepresentation progression interface to configure the GUI of one or moreclient devices to indicate a second topic object as the active topicobject by one or more visual emphasis elements. Such a transmission ofthe shared dynamic collaborative presentation progression interface mayoverwrite the previous transmission of the shared dynamic collaborativepresentation progression interface (e.g., comprising an active visualemphasis element of the [first] topic object) on the client device101A-101N.

With reference to FIG. 6 , a flowchart is provided broadly illustratinga series of operations or process blocks for determining a presentingorder and causing display of visual representations of each of theparticipating user identifiers in accordance with such determined orderin an audio-video conference presentation, in accordance with someexample embodiments of the present disclosure. The operationsillustrated in FIG. 6 may, for example, be performed by, with theassistance of, and/or under the control of one or more apparatuses, suchas shared dynamic collaborative presentation progression interfaceserver 210, as described above. In this regard, performance of theoperations may invoke one or more of memory 201, processor 202,input/output circuitry 203, communications circuitry 204, and/orcollaborative contextual summary interface circuitry 205. Certainoperations may be considered optional, as indicated by the dashed lines.

As shown in operation 605, the apparatus (e.g., shared dynamiccollaborative presentation progression interface server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, and/or the like, for identifying a first participatinguser identifier of the plurality of participating user identifiersassociated with the first topic object. In some embodiments, theidentification of a first participating user identifier in the pluralityof participating user identifiers associated with the first topic objectmay be performed in response to the shared dynamic collaborativepresentation progression interface server 210 receiving an identifyrandom presentation order event. In some embodiments, a second topicobject may be identified as an active topic object and a secondparticipating user identifier may be identified by the shared dynamiccollaborative presentation progression interface server 210.

In some embodiments, the identify random presentation order event maycomprise an electronic request transmitted from one or moreparticipating client devices and/or an administrative client device (notpictured, but which comprises the same circuitry and capabilities asthat shown in apparatus 300), wherein the administrative client devicemay be configured to access certain specifications of the audio-videoconference presentation that other client devices, or participatingclient devices, cannot. In some non-limiting examples, a user of the oneor more client devices (e.g., a user associated with a participatingclient devices and/or a user associated with an administrative device)may select via a configured GUI of the client device (e.g., configuredby the shared dynamic collaborative presentation progression interface)to select a random presentation order event. In some embodiments, therandom presentation order event may cause the topic object sequence setto be configured in a randomized order. For example, a randomized ordermay be caused by a random number generator or pseudo-random numbergenerator. In some embodiments, the random presentation order event maycause the topic object sequence set to be configured in a randomizedorder based on the order of the participating users of the participatingclient devices joining the audio-video conference presentation (e.g.,order by which the participating users joined the meeting). In someembodiments, the random presentation order event may cause the topicobject sequence set to be configured in a randomized order based on theone or more time zones associated with the participating client devices.By way of non-limiting example, the one or more time zones of theparticipating client devices may be used to determine the topic objectsequence set in a randomized order as an order of time zones for theparticipating client devices, such as a randomized order based onearlier time zones (e.g., a time zone comprising an earlier time (e.g.,10 am CST) may indicate the participating user associated with theearlier time zone will go before a participating user associated with alater time zone (e.g., 11 am EST)). By way of non-limiting example, theone or more time zones of the participating client devices may be usedto determine the topic object sequence set in a randomized order as anorder of time zones for the participating client devices, such as a anorder of time zones in a later time zone (e.g., a participating user ina later time zone such as 12 pm CST may go before a participating userin an earlier time zone such as 11 PST). In some embodiments, once therandom presentation order event is selected by a user of the one or moreclient devices, a request may be transmitted to the shared dynamiccollaborative presentation progression interface server 210 comprisingthe random presentation order event. The shared dynamic collaborativepresentation progression interface server 210 may collect the randompresentation order event and identify said random presentation orderevent as instructions to randomize the topic objects, of the topicobject sequence set, and/or presenters of the audio-video conferencepresentation and transmit the randomized topic objects to one or moreusers of the client devices as configured GUI. By way of non-limitingexample, a random presentation order event may be indicated to a uservia an electronically selectable element, such as “button” configured onthe client device of the user, like that shown 1410 of FIG. 14(indicating a selectable element which reads, “Random order”).

As shown in operation 610, the apparatus (e.g., shared dynamiccollaborative presentation progression interface server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, and/or the like, to cause display of a visualrepresentation of the first participating user identifier in associationwith the visual representation of the first topic object. In someembodiments, the display of the visual representation of the firstparticipating user identifier in association with the visualrepresentation of the first topic object may be in response to theshared dynamic collaborative presentation progression interface server210 transmitting the shared dynamic collaborative presentationprogression interface for configuring of a GUI on one or more clientdevices.

In some embodiments, the shared dynamic collaborative presentationprogression interface server 210 may transmit one or more interfaceelements (e.g., a shared dynamic collaborative presentation progressioninterface) to one or more client devices, including participating clientdevices, in order to display a visual representation of the firstparticipating user identifier in association with the first topicobject. By way of non-limiting example, a visual representation of thefirst participating user identifier may comprise an identifier of a userof a participating client device such as a name of the user, a usernameof the user, an icon or graphic associated with the user, a picturegraphic (e.g., a picture of the user), and/or other identifying elementsof the user. By way of non-limiting example, a random presentation orderevent may be indicated to a user via an electronically selectableelement, such as “button” configured on the client device of the user,like that shown in 905 of FIG. 9 (indicating a participating user'sname); 1205 of FIG. 12 (indicating a picture graphic of a userassociated with topic object 1220), 1305 of FIG. 13 (indicating aplurality of picture graphics associated with a plurality of users ofthe audio-video presentation service); 1415 of FIG. 14 (indicating apicture graphic of a participating user); and 1615, 1630, 1645, and 1660of FIG. 16 .

As shown in operation 615, the apparatus (e.g., shared dynamiccollaborative presentation progression interface server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, and/or the like, to determine a presenting order of theremaining participating user identifiers associated with the first topicobject. In some embodiments, the shared dynamic collaborativepresentation progression interface server 210 determines a randomizedpresenting order (e.g., of topic objects and/or participating useridentifiers) using one or more randomizer methods. In some embodiments,such randomizer methods comprise at least one of a random numbergenerator or a pseudo-random number generator. In some embodiments, theentire random presenting order is defined at once. Additionally oralternatively, a randomizer method is used anew at each position of thegenerated presentation order.

As shown in operation 620, the apparatus (e.g., shared dynamiccollaborative presentation progression interface server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, and/or the like, to cause the display of a visualrepresentation of each of the remaining participating user identifiersin the determined order in association with an upcoming presenterinterface element in the visual representation of the first topicobject. In some embodiments, once the presentation order for the one ormore participating user identifiers are determined by the shared dynamiccollaborative presentation progression interface server 210, the shareddynamic collaborative presentation progression interface server 210 maytransmit an updated shared dynamic collaborative presentationprogression interface and/or an instructions set for updating the shareddynamic collaborative presentation progression interface to includevisual representation(s) of the remaining participating user identifiersin such defined order. By way of non-limiting example, the shareddynamic collaborative presentation progression interface used toconfigure the GUI of the one or more participating client devices may beshown as interface 1500 of FIG. 15 , which may further comprise a visualrepresentation list of the upcoming participating user identifiers(e.g., 1515, 1520, 1525, etc.) in the determined presentation order.

Additionally or alternatively, in some embodiments, the presenting orderof the participating user identifiers in association with the topicobject sequence set is defined by the topic object sequence set. In someembodiments, the topic object sequence set may be identified and/orgenerated by one or more users of the participating client devices(e.g., prior to and/or during the audio-video conference presentation).In some embodiments, the topic object sequence set may comprise a userinteracting with a configured GUI (e.g., configured by the shareddynamic collaborative presentation progression interface server 210) toindicate, assign, and/or request one or more user identifiers for eachof the one or more topic objects. By way of non-limiting example, theindication, assignment, and/or request by one or more users of theparticipating client device may be indicated by an electronicallyselectable element of the configured GUI (e.g., configured by the shareddynamic collaborative presentation progression interface server 210) ofthe participating client device, such as that shown at 1015 at FIG. 10(indicating a selectable indicia, such as a button which reads, “Assignowner” for the one or more topic objects of list 1010). In someembodiments, and in response to the indication, assignment, and/orrequest by one or more users of the participating client devices, theshared dynamic collaborative presentation progression interface server210 may receive an assigned user identifier for each of the one or moretopic objects of the topic object sequence set from the one or moreparticipating client devices. In some embodiments, such indication,assignment, and/or request is received prior to the start of theaudio-video conference presentation. Additionally or alternatively, suchindication, assignment, and/or request is received in real-time duringthe audio-video conference presentation.

In some embodiments, the active audio-video conference presentation isassociated with a presentation identifier and the topic object sequenceset is associated with the presentation identifier. For example, in someembodiments, prior to the start of the audio-video conferencepresentation, a topic object sequence set is defined by one or moreparticipating users and associated with the audio-video conferencepresentation such that the topic object sequence set is automaticallyretrieved, displayed with, and/or associated with the audio-videoconference presentation at the start of the audio-video conferencepresentation. In some embodiments, such association is accomplished byassociating each with the unique presentation identifier. In suchembodiments, no manual selection from a user is required during theaudio-video conference presentation to identify the associated topicobject sequence set (e.g., agenda). Additionally or alternatively, oneor more participating users may manually select an agenda (e.g., topicobject sequence set) in real-time at the time of the audio-videoconference presentation. With reference to FIG. 7 , a flowchart isprovided broadly illustrating another series of operations or processblocks for retrieving a topic object sequence set based on an agendaobject identifier identified in an agenda object selection request froma participating client device, in accordance with some exampleembodiments of the present disclosure. The operations illustrated inFIG. 7 may, for example, be performed by, with the assistance of, and/orunder the control of one or more apparatuses, such as shared dynamiccollaborative presentation progression interface server 210, asdescribed above. In this regard, performance of the operations mayinvoke one or more of memory 201, processor 202, input/output circuitry203, communications circuitry 204, and/or collaborative contextualsummary interface circuitry 205. Certain operations may be consideredoptional, as indicated by the dashed lines.

As shown in operation 705, the apparatus (e.g., shared dynamiccollaborative presentation progression interface server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, and/or the like, for receiving a display collaborativeconference presentation interface request, wherein the displaycollaborative conference presentation interface request comprises aparticipating user identifier. In some embodiments, the displaycollaborative conference presentation interface request may betransmitted to the shared dynamic collaborative presentation progressioninterface server 210 from a participating client device by a specifieduser of the participating client device. In some embodiments, thedisplay collaborative conference presentation interface request may betransmitted to a schedule API such as a calendar service (e.g., from anemail service such as Outlook®, Gmail®, Yahoo®), business collaborationsoftware tools (e.g., Slack® or other such business collaboration tools)from a participating client device by a specified user of theparticipating client device to access and/or receive one or moresequence topic object sets. In some embodiments, the displaycollaborative conference presentation interface request may comprise arequest (e.g., electronic request) and/or indication from the user ofthe participating client device to configure the GUI of theparticipating client device to show one or more sequence topic objectsets generated by the user of the participating client device. By way ofnon-limiting example, Alice may generate a plurality of sequence topicobject sets for a plurality of audio-video conference presentations, andthis plurality of sequence topic object sets may be stored locally onthe participating client device and/or on the shared dynamiccollaborative presentation progression interface server 210. By way ofnon-limiting example, Alice may transmit a request to the shared dynamiccollaborative presentation progression interface server 210 to displaythe plurality of sequence topic object sets on the participating clientdevice by transmitting a display collaborative conference presentationinterface request. In some embodiments, the display collaborativeconference presentation interface request may comprise a participatinguser identifier (e.g., a participating user identifier identifying Aliceas the participating user transmitting the display collaborativeconference presentation interface request).

As shown in operation 710, the apparatus (e.g., shared dynamiccollaborative presentation progression interface server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, and/or the like, for querying a repository for agendaobjects associated with the user identifier. In some embodiments, and inresponse to receiving the display collaborative presentation interfacerequest, the shared dynamic collaborative presentation progressioninterface server 210 may query a repository (e.g., a shared dynamiccollaborative presentation progression interface repository 215) for thetopic object sequence sets associated with the participating useridentifier received and identified in operation 705. In someembodiments, the shared dynamic collaborative presentation progressioninterface repository 215 may store the one or more topic object sequencesets of one or more participating users of the participating userdevices which may be in communication with the collaborativepresentation progression interface management system 200 and/or the ashared dynamic collaborative presentation progression interface server210. By way of non-limiting example, each of the one or more topicobject sequence sets may be stored in the a shared dynamic collaborativepresentation progression interface repository 215 in specific storagesubsystems (e.g., sub-repositories) which may each be associated with aspecific participating user identifier like that received in operation705. The shared dynamic collaborative presentation progression interfaceserver 210 may query the a shared dynamic collaborative presentationprogression interface repository 215 to locate the one or more topicobject sequence sets associated with a particular participating useridentifier.

As shown in operation 715, the apparatus (e.g., shared dynamiccollaborative presentation progression interface server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, and/or the like, for causing display of a collaborativeconference presentation interface to the participating client deviceassociated with the participating user identifier in association withthe active audio-video conference presentation. In some embodiments, thecollaborative conference presentation interface may comprise a renderedlisting of agenda objects returned by the query. By way of non-limitingexample, the rendered listing of agenda objects may include a title foreach for each of the topic object sequence sets generated and/or createdby the participating user associated with the participating useridentifier. For example, a participating user may generate a title of atopic object sequence set along with the each topic object of the topicobject sequence set in one or more interfaces transmitted by the shareddynamic collaborative presentation progression interface server 210 tothe participating client device. Such an example interface may be shownas interface 800 of FIG. 8 , which may comprise title 805 (e.g., a topicobject sequence set description). In some embodiments, the exampleinterface to generate the topic object sequence set may also comprisefillable content on the interface (e.g., fillable by a participatinguser) to include the one or more topic objects of the topic objectsequence set, such as the list of topic objects in list 815, which maybe identified generally as the topics 810 covered by the specific topicobject sequence set described by title 805.

In some embodiments, collaborative conference presentation interface maycomprise one or more titles of the topic object of each of the topicobjects associated with the participating user identifier andtransmitted to the participating client device for display. By way ofnon-limiting example, such a collaborative conference presentationinterface may be shown as interface 900 of FIG. 9 , which may comprise arendered listing of agenda objects 910 returned by the query of theshared dynamic collaborative presentation progression interfacerepository. In some embodiments, each agenda object (e.g., topic objectsequence set) of the rendered listing of agenda objects may comprise thetitle of the topic object sequence set, such as that shown bynon-limiting example as element 915 which reads, “Ivy Technology Demo.”In some embodiments, a new agenda may be added to the agenda objects ofthe rendered listing of agenda objects by a selectable element of theinterface, such as element 920 of interface 920. By way of non-limitingexample, when a user selects (e.g., clicks) element 920 to generate anew agenda, the participating client device's interface may beconfigured to show interface 800 of FIG. 8 for a user to input one ormore text objects to disclose the one or more topic objects, topicobject sequence set description (e.g., such as a summary), and/or atitle associated with the topic object sequence set.

In some embodiments, each of the agenda objects returned by the querymay be configured to be selectable. By way of non-limiting example, theshared dynamic collaborative presentation progression interface server210 may configure the GUI of a participating client device such that theclient devices shows an interface (e.g., a collaborative conferencepresentation interface) comprising one or more agenda objects associatedwith the participating user identifier. Such agenda objects rendered onthe configured GUI may comprise capabilities for user selection (e.g., auser may electronically request to access an agenda, topic objectsequence set, of the agenda identifiers). Once selected by a user, theparticipating client device may transmit an agenda object selectionrequest to the shared dynamic collaborative presentation progressioninterface server 210 to identify an agenda object selection request.

As shown in operation 720, the apparatus (e.g., shared dynamiccollaborative presentation progression interface server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, and/or the like, for identifying an agenda objectselection request. By way of non-limiting example, the agenda objectselection request may comprise data indicative of a user's selection ofa particular agenda object to be presented in an audio-video conferencepresentation. In some embodiments, the agenda object selection requestcomprises an agenda object identifier. In some embodiments, once theshared dynamic collaborative presentation progression interface server210 has received the agenda object selection request from aparticipating client device, the shared dynamic collaborativepresentation progression interface server 210 may further identifyand/or collect an agenda object identifier transmitted with the agendaobject selection request.

As shown in operation 725, the apparatus (e.g., shared dynamiccollaborative presentation progression interface server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, and/or the like, for retrieving the topic object sequenceset based on the agenda object identifier from the repository. In someembodiments, the agenda object identifier may comprise computer codeidentifying a specific topic object sequence set stored within a shareddynamic collaborative presentation progression interface repository 215in communication with the shared dynamic collaborative presentationprogression interface server 210. For example, the shared dynamiccollaborative presentation progression interface server 210 may querythe shared dynamic collaborative presentation progression interfacerepository 215, based upon the agenda object identifier, to identify andreceive the topic object sequence set of the associated agenda objectidentifier from the shared dynamic collaborative presentationprogression interface repository 215. In some embodiments, the topicobject sequence set may comprise any of a plurality of elements hereindescribed (e.g., a first topic object, one or more user identifiersassigned to each of the topic objects, one or more target timesassociated with one or more topics objects, etc.).

FIGS. 4A, 4B, 5, 6, and 7 thus illustrate flowcharts and signal diagramsdescribing the operation of apparatuses, methods, systems, and computerprogram products according to example embodiments contemplated herein.It will be understood that each flowchart block, and combinations offlowchart blocks, may be implemented by various means, such as hardware,firmware, processor, circuitry, and/or other devices associated withexecution of software including one or more computer programinstructions. For example, one or more of the operations described abovemay be implemented by an apparatus executing computer programinstructions. In this regard, the computer program instructions may bestored by a memory 201 of the shared dynamic collaborative presentationprogression interface server 210 and executed by a processor 202 of theshared dynamic collaborative presentation progression interface server210. As will be appreciated, any such computer program instructions maybe loaded onto a computer or other programmable apparatus (e.g.,hardware) to produce a machine, such that the resulting computer orother programmable apparatus implements various functions, includingthose functions specified in the flowchart blocks. These computerprogram instructions may also be stored in a computer-readable memorythat may direct a computer or other programmable apparatus to functionin a particular manner, such that the instructions stored in thecomputer-readable memory produce an article of manufacture, theexecution of which implements the functions specified in the flowchartblocks. The computer program instructions may also be loaded onto acomputer or other programmable apparatus to cause a series of operationsto be performed on the computer or other programmable apparatus toproduce a computer-implemented process such that the instructionsexecuted on the computer or other programmable apparatus provideoperations for implementing the functions specified in the flowchartblocks.

The flowchart blocks support combinations of means for performing thespecified functions and combinations of operations for performing thespecified functions. It will be understood that one or more blocks ofthe flowcharts, and combinations of blocks in the flowcharts, can beimplemented by special purpose hardware-based computer systems whichperform the specified functions, or combinations of special purposehardware with computer instructions.

Thus, particular embodiments of the subject matter have been described.While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as description offeatures specific to particular embodiments of particular inventions.Other embodiments are within the scope of the following claims. Certainfeatures that are described herein in the context of separateembodiments can also be implemented in combination in a singleembodiment.

Conversely, various features that are described in the context of asingle embodiment can also be implemented in multiple embodimentsseparately or in any suitable sub-combination. Moreover, althoughfeatures may be described above as acting in certain combinations andeven initially claimed as such, one or more features from a claimedcombination can in some cases be excised from the combination, and theclaimed combination may be directed to a sub-combination or variation ofa sub-combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults, unless described otherwise. In certain circumstances,multitasking and parallel processing may be advantageous. Moreover, theseparation of various system components in the embodiments describedabove should not be understood as requiring such separation in allembodiments, and it should be understood that the described programcomponents and systems can generally be integrated together in a singlesoftware product or packaged into multiple software products. Anyoperational step shown in broken lines in one or more flow diagramsillustrated herein are optional for purposes of the depicted embodiment.

In some cases, the actions recited in the claims can be performed in adifferent order and still achieve desirable results. In addition, theprocesses depicted in the accompanying figures do not necessarilyrequire the particular order shown, or sequential order, to achievedesirable results, unless described otherwise. In certainimplementations, multitasking and parallel processing may beadvantageous.

CONCLUSION

Many modifications and other embodiments of the present disclosure setforth herein will come to mind to one skilled in the art to which thisdisclosure pertains having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the disclosure is not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Moreover, although the foregoing descriptions and the associateddrawings describe example embodiments in the context of certain examplecombinations of elements and/or functions, it should be appreciated thatdifferent combinations of elements and/or functions may be provided byalternative embodiments without departing from the scope of the appendedclaims. In this regard, for example, different combinations of elementsand/or functions than those explicitly described above are alsocontemplated as may be set forth in some of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

1. An apparatus configured to manage a shared dynamic collaborativepresentation progression interface in association with an audio-videoconferencing interface service, the apparatus comprising at least oneprocessor and at least one memory, the at least one memory havingcomputer-coded instructions therein, wherein the computer-codedinstructions are configured to, in execution with the at least oneprocessor, cause the apparatus to: monitor an active audio-videoconference presentation that is configured for rendering to respectivedisplays of a plurality of participating client devices by theaudio-video conferencing interface service; generate a shared dynamiccollaborative presentation progression interface, wherein the shareddynamic collaborative presentation progression interface is associatedwith a topic object sequence set, the shared dynamic collaborativepresentation progression interface comprising a visual representation ofthe topic object sequence set and wherein the shared dynamiccollaborative presentation progression interface is configured forrendering to the respective displays of the plurality of participatingclient devices in association with the active audio-video conferencepresentation; transmit the shared dynamic collaborative presentationprogression interface to the plurality of participating client devices;receive an initiate topic object sequence set event from at least oneparticipating client device of the plurality of participating clientdevices; in response to receiving the initiate topic object sequence setevent, identify a first topic object of the topic object sequence set asan active topic object; and update the shared dynamic collaborativepresentation progression interface to cause rendering of at least anactive visual emphasis element in association with a visualrepresentation of the first topic object, and wherein the visualrepresentation of the first topic object comprises an identification ofthe first topic object, wherein the active visual emphasis elementvisually identifies the first topic object as the active topic object ascompared to a visual representation of the one or more non-active topicobjects of the topic object sequence set concurrently rendered to theupdated shared dynamic collaborative presentation progression interface.2. The apparatus of claim 1, wherein the updated shared dynamiccollaborative presentation progression interface further comprises avisual representation of an elapsed time object displayed in associationwith the first topic object.
 3. The apparatus of claim 2, wherein theelapsed time object corresponds to a timer activated by the apparatus inassociation with identifying the first topic object as the active topicobject.
 4. (canceled)
 5. The apparatus of claim 2, wherein thecomputer-coded instructions are further configured to, in execution withthe at least one processor, cause the apparatus to: receive a topicobject progression event from at least one participating client deviceof the plurality of participating client devices; de-identify the firsttopic object as the active topic object; identify a second topic objectin the topic object sequence set as the active topic object; generate atransition topic object sequence instructions set based on the topicobject progression event; and output the transition topic objectsequence instructions set to the plurality of participating clientdevices for updating the shared dynamic collaborative presentationprogression interface, wherein updating the shared dynamic collaborativepresentation progression interface comprises causing: stopping of therendering of the active visual emphasis element in association with thevisual representation of the first topic object; and rendering of theactive visual emphasis element in association with the visualrepresentation of the second topic object.
 6. The apparatus of claim 5,wherein de-identifying the first topic object as the active topic objectcomprises: dissociating an active topic object identifier from the firsttopic object; associating the first topic object with a completed topicobject identifier; and storing the elapsed time object coinciding withthe receipt of the topic object progression event in association withthe completed first topic object.
 7. The apparatus of claim 5, whereinthe computer-coded instructions are further configured to, in executionwith the at least one processor, cause the apparatus to: in associationwith causing stopping of the rendering of the active visual emphasiselement with respect to the visual representation of the first topicobject, cause display of a completion indicator in association with thevisual representation of the first topic object.
 8. (canceled) 9.(canceled)
 10. The apparatus of claim 5, wherein identifying the secondtopic object in the topic object sequence set as the active topic objectcomprises associating the second topic object with an active topicobject identifier.
 11. The apparatus of claim 5, wherein a firstparticipating user identifier is associated with the first topic objectand a second participating user identifier is associated with the secondtopic object and wherein the computer-coded instructions are furtherconfigured to, in execution with the at least one processor, cause theapparatus to: display a visual representation of the first participatinguser identifier in association with the visual representation of thefirst topic object; and display a visual representation of the secondparticipating user identifier in association with the visualrepresentation of the second topic object.
 12. The apparatus of claim11, wherein the computer-coded instructions are further configured to,in execution with the at least one processor, cause the apparatus to: inresponse to identifying the first topic object of the topic objectsequence set as the active topic object, transmit a display upcomingpresenter notification event to the participating client deviceassociated with the second participating user identifier.
 13. Theapparatus of claim 1, wherein a plurality of participating useridentifiers are associated with the first topic object and wherein thecomputer-coded instructions are further configured to, in execution withthe at least one processor, cause the apparatus to: in response toreceiving an identify random presentation order event, identify a firstparticipating user identifier of the plurality of participating useridentifiers associated with the first topic object; cause display of avisual representation of the first participating user identifier inassociation with the visual representation of the first topic object;determine a presenting order of the remaining participating useridentifiers associated with the first topic object; and cause display ofvisual representations of each of the remaining participating useridentifiers in the determined order in association with an upcomingpresenter interface element in the visual representation of the firsttopic object.
 14. (canceled)
 15. The apparatus of claim 1, wherein theactive audio-video conference presentation is associated with apresentation identifier and the topic object sequence set is associatedwith the presentation identifier.
 16. The apparatus of claim 1, whereinthe computer-coded instructions are further configured to, in executionwith the at least one processor, cause the apparatus to: receive adisplay collaborative conference presentation interface request, whereinthe display collaborative conference presentation interface requestcomprises a participating user identifier; query a repository for agendaobjects associated with the user identifier; cause display of acollaborative conference presentation interface to the participatingclient device associated with the participating user identifier inassociation with the active audio-video conference presentation, whereinthe collaborative conference presentation interface comprises a renderedlisting of agenda objects returned by the query and wherein each of theagenda objects is configured to be selectable; identify an agenda objectselection request, wherein the agenda object selection request comprisesan agenda object identifier; and retrieve the topic object sequence setbased on the agenda object identifier from the repository.
 17. Theapparatus of claim 1, wherein the shared dynamic collaborativepresentation progression interface comprises a visual representation ofthe topic object sequence set.
 18. The apparatus of claim 17, whereineach of the topic objects of the topic object sequence set areassociated with a respective target time and the computer-codedinstructions are further configured to, in execution with the at leastone processor, cause the apparatus to: display a visual representationof the respective target time in association with each topic object thatis not associated with a completed topic object identifier or an activetopic object identifier.
 19. The apparatus of claim 18, wherein thecomputer-coded instructions are further configured to, in execution withthe at least one processor, cause the apparatus to: determine an elapsedtime for each completed topic object, wherein a completed topic objectis a topic object associated with a completed topic object identifier;display a visual representation of the respective elapsed time inassociation with each completed topic object; determine a visualemphasis element for each completed topic object based at least in parton the respective target time, wherein each visual emphasis elementemploys a contextually relevant coloring scheme to visually indicate acomparison of the elapsed time for the completed topic object to therespective target time of each completed topic object; and apply thedetermined visual emphasis elements to the visual representations of therespective elapsed time in association with each completed topic object.20. A computer-implemented method for managing a shared dynamicpresentation progression interface in association with an audio-videoconferencing interface service, the computer-implemented methodcomprising: monitoring an active audio-video conference presentationthat is configured for rendering to respective displays of a pluralityof participating client devices by the audio-video conferencinginterface service; generating a shared dynamic collaborativepresentation progression interface, wherein the shared dynamiccollaborative presentation progression interface is associated with atopic object sequence set, the shared dynamic collaborative presentationprogression interface comprising a visual representation of the topicobject sequence set and wherein the shared dynamic collaborativepresentation progression interface is configured for rendering to therespective displays of the plurality of participating client devices inassociation with the active audio-video conference presentation;transmitting the shared dynamic collaborative presentation progressioninterface to the plurality of participating client devices; receiving aninitiate topic object sequence set event from at least one participatingclient device of the plurality of participating client devices; inresponse to receiving the initiate topic object sequence set event,identify a first topic object of the topic object sequence set as anactive topic object; and updating the shared dynamic collaborativepresentation progression interface to cause rendering of at least anactive visual emphasis element in association with a visualrepresentation of the first topic object, wherein the visualrepresentation of the first topic object comprises an identification ofthe first topic object, and wherein the active visual emphasis elementvisually identifies the first topic object as the active topic object ascompared to a visual representation of the one or more non-active topicobjects of the topic object sequence set concurrently rendered to theupdated shared dynamic collaborative presentation progression interface.21. The computer-implemented method of claim 20, further comprising:displaying, on a visual representation associated of the shared dynamiccollaborative presentation progression interface, an elapsed time objectin association with the first topic object.
 22. The computer-implementedmethod of claim 21, further comprising: receiving a topic objectprogression event from at least one participating client device of theplurality of participating client devices; de-identifying the firsttopic object as the active topic object; identifying a second topicobject in the topic object sequence set as the active topic object;generating a transition topic object sequence instructions set based onthe topic object progression event; and outputting the transition topicobject sequence instructions set to the plurality of participatingclient devices for updating the shared dynamic collaborativepresentation progression interface, wherein updating the shared dynamiccollaborative presentation progression interface comprises causing:stopping of the rendering of the active visual emphasis element inassociation with the visual representation of the first topic object;and rendering of the active visual emphasis element in association withthe visual representation of the second topic object.
 23. Thecomputer-implemented method of claim 22, further comprising:de-identifying the first topic object as the active topic objectcomprising: dissociating an active topic object identifier from thefirst topic object; associating the first topic object with a completedtopic object identifier; and storing the elapsed time object coincidingwith the receipt of the topic object progression event in associationwith the completed first topic object.
 24. The computer-implementedmethod of claim 22, further comprising: causing, in association withcausing stopping of the rendering of the active visual emphasis elementwith respect to the visual representation of the first topic object,display of a completion indicator in association with the visualrepresentation of the first topic object.
 25. (canceled)
 26. Thecomputer-implemented method of claim 22, further comprising: identifyingthe second topic object in the topic object sequence set as the activetopic object comprises associating the second topic object with anactive topic object identifier.
 27. The computer-implemented method ofclaim 22, further comprising: displaying a visual representation of thefirst participating user identifier in association with the visualrepresentation of the first topic object; and displaying a visualrepresentation of the second participating user identifier inassociation with the visual representation of the second topic object.28. The computer-implemented method of claim 27, further comprising:transmitting, in response to identifying the first topic object of thetopic object sequence set as the active topic object, a display upcomingpresenter notification event to the participating client deviceassociated with the second participating user identifier.
 29. Thecomputer-implemented method of claim 20, further comprising:identifying, in response to receiving an identify random presentationorder event, a first participating user identifier of the plurality ofparticipating user identifiers associated with the first topic object;causing display of a visual representation of the first participatinguser identifier in association with the visual representation of thefirst topic object; determining a presenting order of the remainingparticipating user identifiers associated with the first topic object;and causing display of visual representations of each of the remainingparticipating user identifiers in the determined order in associationwith an upcoming presenter interface element in the visualrepresentation of the first topic object.
 30. The computer-implementedmethod of claim 20, further comprising: receiving a displaycollaborative conference presentation interface request, wherein thedisplay collaborative conference presentation interface requestcomprises a participating user identifier; querying a repository foragenda objects associated with the user identifier; causing display of acollaborative conference presentation interface to the participatingclient device associated with the participating user identifier inassociation with the active audio-video conference presentation, whereinthe collaborative conference presentation interface comprises a renderedlisting of agenda objects returned by the query and wherein each of theagenda objects is configured to be selectable; identifying an agendaobject selection request, wherein the agenda object selection requestcomprises an agenda object identifier; and retrieving the topic objectsequence set based on the agenda object identifier from the repository.31. The computer-implemented method of claim 20, further comprising:displaying a visual representation of the respective target time inassociation with each topic object that is not associated with acompleted topic object identifier or an active topic object identifier.32. The computer-implemented method of claim 31, further comprising:determining an elapsed time for each completed topic object, wherein acompleted topic object is a topic object associated with a completedtopic object identifier; displaying a visual representation of therespective elapsed time in association with each completed topic object;determining a visual emphasis element for each completed topic objectbased at least in part on the respective target time, wherein eachvisual emphasis element employs a contextually relevant coloring schemeto visually indicate a comparison of the elapsed time for the completedtopic object to the respective target time of each completed topicobject; and applying the determined visual emphasis elements to thevisual representations of the respective elapsed time in associationwith each completed topic object.
 33. A computer-program productcomprising at least one non-transitory computer-readable storage mediumhaving computer-readable program code thereon that, in execution with atleast one process, configures the computer program product for:monitoring an active audio-video conference presentation that isconfigured for rendering to respective displays of a plurality ofparticipating client devices by the audio-video conferencing interfaceservice; generating a shared dynamic collaborative presentationprogression interface, wherein the shared dynamic collaborativepresentation progression interface is associated with a topic objectsequence set, the shared dynamic collaborative presentation progressioninterface comprising a visual representation of the topic objectsequence set and wherein the shared dynamic collaborative presentationprogression interface is configured for rendering to the respectivedisplays of the plurality of participating client devices in associationwith the active audio-video conference presentation; transmitting theshared dynamic collaborative presentation progression interface to theplurality of participating client devices; receiving an initiate topicobject sequence set event from at least one participating client deviceof the plurality of participating client devices; in response toreceiving the initiate topic object sequence set event, identify a firsttopic object of the topic object sequence set as an active topic object;and updating the shared dynamic collaborative presentation progressioninterface to cause rendering of at least an active visual emphasiselement in association with a visual representation of the first topicobject, wherein the visual representation of the first topic objectcomprises an identification of the first topic object, and wherein theactive visual emphasis element visually identifies the first topicobject as the active topic object as compared to a visual representationof the one or more non-active topic objects of the topic object sequenceset concurrently rendered to the updated shared dynamic collaborativepresentation progression interface.
 34. The apparatus of claim 1,wherein the active visual emphasis element in association with thevisual representation of the first topic object is positioned proximateto the visual representation of the one or more non-active topic objectsin the shared dynamic collaborative presentation progression interface.35. The apparatus of claim 1, wherein the visual representation of theone or more non-active topic objects is depicted as a summary listing ofthe non-active topic objects, the visual representation of the one ormore non-active topic objects positioned proximate to the visualrepresentation of the first topic object in the shared dynamiccollaborative presentation progression interface.
 36. The apparatus ofclaim 1, wherein the rendering of the active audio-video conferencepresentation is rendered concurrently with the shared dynamiccollaborative presentation progression interface to the respectivedisplays of the plurality of participating client devices.